Drives not mapping in XP with profile path set in AD? Argh!
Hi - got a really really odd problem that's been mashing my swede for a day now.
Building a new domain here, imported all users ok from our current domain and aiming to cut over during the summer. Have test vms of XP and Win7 clients.
What's weird is using the XP client (Win 7 clients untested as yet as their .v2 profiles aren't sorted), with GP extensions installed, will not map network drives either from the Preferences in GP nor from a startup script. Most file servers are Linux/Samba on the 'old', current domain, but usernames and passwords are the same and regularly updated so rights are not an issue.
Here's what I've found so far, and VERY odd it is:
- Administrators are unaffected by this crappery.
- When the user in question has no profile path set in AD, the drives map fine as per the script or Preferences or whichever method I turn on at the time. When it's set in AD though this happens.
- Application Log on the vm gives two odd errors ON ONE XP VM, BUT NOT A FRESH ONE:
Event ID: 1085 (GP client side extensions failed to execute)
Event ID: 8196 (client side extension unhandled exception 0xc0000005 in threadEntry : client main)
- UNC path to the batch file option of mapping works ok and the batch file runs BUT prompts for username and password before mapping the drives.
Anyone have any idea what on earth is going on? Never seen anything like this ever before, and I'm on day 2 of it now with no idea :/ Without that profile path (again to a Samba server) the drives just map fine!
Cheers for reading this far if you're not terrified yet!