Logon scripts failing on a cross domain login

[ws_avd]

[TD="bgcolor: #F5F5F5"]Hi,

I'm hoping for some help related to login scripts when logging onto another domain. Here is the scenario:
We have two domains DOM_A (server2003) and DOM_B (server2008). They are set up in a trust relationship and there is no problem opening files or browsing computers cross domain.

But login scripts do not run when logging onto a DOM_B machine with a DOM_A account. For example we login with DOM_A\user to machine.DOM_B.local.

The login script contains the drive mappings and these do not appear because of this problem.

I have already done the following:
- Checked that I have the "Allow Cross-Forest User Policy and Roaming User Profiles" policy enabled on the machine in question.
- Added the DNS suffix DOM_A.local to the machine in DOM_B via Group Policy.
- Checked DOM_B DNS and ensured that the DC for DOM_A was not also in the DOM_B DNS list.

None of this has helped and the logon script still does not run. There is no problem reaching or running the script once logged in. But something is stopping it from running during logon. Either it's a group policy issue or a DNS one. I just cant figure out which or how to fix it.

Any help would be appreciated.

[ws_avd]

Hi,

 

Just to let anyone reading this know. I have resolved this now.

 

The "Allow Cross-Forest..." and DNS Suffix things are really all there is to it apart from setting up the Trust Relationship correctly.

 

For me the issue was that I had a User Policy applied to the machine that had loopback processing on and was enforced. Which I think meant it always won and overrode the user policy coming from the other domain. I removed the computer from that OU and the script started running.

 

So, tip is, check that you don't have any enforced loop back processed GPO's applied to a PC you want users to login to from another domain (and still run their logon scripts).