We have Windows2003 Server SP1 with XP Pro SP1 workstations....
- Gpresult The User Does Not Have Rsop Data
- Do Not Have Rsop Data
- Does Not Have Rsop Data
- Does Not Have Rsop Data Group Policy
Now right click the 'Resultant Set of Policy' and choose 'Generate RSoP data'. Click 'Next' then choose 'logging mode' and click 'Next. Choose the 'Another computer' type in the name and click:Next. Now see in the next screen if you can choose an existing user and if the users populate in the window. Gpresult /R INFO: The user adm.test does not have RSoP data. You try to do it remotely and it fails as well. Gpresult /S DDD9D5 /SCOPE COMPUTER /R INFO: The user does not have RSoP data. While the gpresult command, using the /h or /s switches, can grab a partial RSoP report, often when running it in a session as a user, it will not get the Computer Policy information due to permissions issues, or if you run that command as an administrator, it will not grab the user policy. The gpresult /v will usually grab a complete report. Click Resultant Set of Policy, click Add, and then click Close in the Add/Remove Standalone Snapin dialog box. Click OK in the Add/Remove dialog box. The Resultant Set of Policy snapin is displayed in the MMC. Click Generate RSOP data on the Action menu. Click Next, click Logging Mode, and then click Next.
Eventually we discoved that the UserPrincipalName in AD had been set for these two users but not for anyone else. (In AD, Properties-Tab Account- field logon name). When we removed this field everything was fine. As we don't normally set this field, perhaps it was set wrong but in any case, FrontMotion didn't like it.
Has anyone else had this problem? We have fixed ours now by removeing but just curious.
Gpresult The User Does Not Have Rsop Data
We have Windows2003 Server SP1 with XP Pro SP1 workstations....We had the problem that with two of our users, when FrontMotion was installed, no GPOs were applied when they logged on. If you tried a 'gpresult', you got the above error message. This was only happening for two of our users though. If we removed FrontMotion, it was fine.
Do Not Have Rsop Data
Eventually we discoved that the UserPrincipalName in AD had been set for these two users but not for anyone else. (In AD, Properties-Tab Account- field logon name). When we removed this field everything was fine. As we don't normally set this field, perhaps it was set wrong but in any case, FrontMotion didn't like it.
Does Not Have Rsop Data
Does Not Have Rsop Data Group Policy
Has anyone else had this problem? We have fixed ours now by removeing but just curious.