Server progress
Posted 29 Sep, 2005 at 02:12 by brent in /System | Permanent link
Well, got mail up and running. Who would have thought that I would not only need to setup another domain controller for oneoddsock but to also find a little checkbox deep in the bowels of the active directory UI to indicate I also want the box to be a global catalog server? That was what was preventing exchange from running correctly. For future reference: Active Directory Sites and Services, Select the desired server in your site, go to NTDS Setting, properties, and select global catalog (not on the connection but on NTDS Settings itself). Then wait for replication to complete before sending servers to the wild blue yonder.
The other problem with mail was that all the script maps were wrong. See, I backed up and restored the IIS metabase to the temp host and of course then install exchange into a slightly different path. Grepping the metabase and correcting these instances has been nothing less than a pain in the ass. I also had to updated my mkexchange.vbs to finally support integrated servers. Not such a bad thing really. Maybe I should post it somewhere for others that have multiple login domains (UPNs) being managed by one domain controller and need to set up log sites in IIS for each login domain.
Please try logging in to the web interface for mail to make sure it is working for you.
Still having a problem with PHP however. It's improved at least from a 500 error to a 404. I suspect another mapping issue since I've also upgraded from 4 to 5 and so there is a name change involved that could snafu a path. Why couldn't they simplify upgrades and use the same name between all versions? Oh right, PHP still uses ini files...