Introduced a new DC a couple of weeks ago (2003 SP2) and have transferred all FSMO roles over and set it as the new DNS that all workstations use the system has been running well so it was time to DCPROMO the old server, the demotion went fine with no errors, netdiag and dcdiag all check ok on the remaining DC's and i've confirmed that the FSMO roles are on the new box.
The old DC held some shared areas and a share containing MSI applications for deployment, since the demotion msi files will not deploy from this server (i can access them manually) but it is accessible as a file server drives map ok and no other errors. If i move an msi package to another server (same permissions) and create a share it will deploy ok from there so i'm sure that the GPO's and DNS are operating ok. I've checked all of the resource records and flushed the DNS cache (the IP hasn't changed but thought i'd try) after this i can still ping the server and access it in every way but packages still fail.
I've been having a read of the document below and am starting to think that it's a kerberos issue SEE: Appendix C: Troubleshooting, Problem: The Application Event Viewer indicates errors that the MSI package installation failed with an error ‘Package source not located’.
I can't try this untill tomorrow but wondered has anyone had this issue before?
Just checking, have you checked the permissions on the distribution share allow domain computers and the everyone group. I had issues where new computers that had just been joined had not had their group membership replicated to to the server that was shareing the files and so was denying them access at first.
The kerberos issue should only apply if the full dns name was used when the application was deployed and should be fine if you have used the machine name.
This server was used to deploy software this morning right before the DCPROMO and it worked just fine i then performed the DCPROMO and the issue started nothing changed in between so the same ACL's that have been working are still set.
The share has everyone set but i've never had domain computers and it's always worked ok. I'm seeing this with clients that are already on the network and new builds as well.
@ Tony: did you see this after demoting a DC as well?