disturbedone
Vendor
I've got a (currently) W2K8R2 domain with XPSP3 clients. One particular VBScript runs in a GPO as a computer startup script that a) checks the resolution and b) based on the resolution runs BGInfo.exe from a specified folder utilizing the relavant *.bgi file to create a desktop that is displayed before the user logs on. This is so we can see what the computer name & IP is before logon. Another GPO as a logon script uses a different *.bgi file to display more information.
That works perfectly on XP but not on Win7. The logon script still works fine but the startup script does not.
The VBScript works perfectly fine if run once a user is logged on. For example, I logon and run the script manually and it creates the appropriate *.jpg file and places it in %windir%system32\oobe\info\backgrounds and names then according to this so the script does work but just not on startup.
I assume this is something to do with Win7 permissions somehow that XP didn't have. Does Win7 not like running VBScript with knowing which user is running it and determining if it should be allowed?
Anyone know a way around this? Either using the existing VBScript or another way (will PowerShell work better?).
That works perfectly on XP but not on Win7. The logon script still works fine but the startup script does not.
The VBScript works perfectly fine if run once a user is logged on. For example, I logon and run the script manually and it creates the appropriate *.jpg file and places it in %windir%system32\oobe\info\backgrounds and names then according to this so the script does work but just not on startup.
I assume this is something to do with Win7 permissions somehow that XP didn't have. Does Win7 not like running VBScript with knowing which user is running it and determining if it should be allowed?
Anyone know a way around this? Either using the existing VBScript or another way (will PowerShell work better?).