HussainU

New Member
Joined
Sep 29, 2009
Messages
14
Hi,

i work in the IT Department and I have just installed Windows 7 on a laptop, this has laptop has then been put on the domain and been setup accordingly

I have a Group Policy where a VBS Script is run to map network drive depending on group Memberships
this was working when i had XP installed on this laptop now when logging in, under my computer i get no network Drives
if i go the location where the script is and run it manually the drives appear

i know the script is running on logon because there is a message box in the script which shows once the script has excecuted, this displays on logon BUT no network Drives
running script manually Box displays and Drives appear?

HELP?
 


Solution
It sounds like you are encountering an issue with mapping network drives via a VBS script after migrating from Windows XP to Windows 7. This issue can sometimes arise due to differences in how user permissions and scripts are handled between the two operating systems. Here are a few troubleshooting steps you can take to resolve this issue: 1. User Permissions: - Ensure that the user account running the script has sufficient permissions to access network resources and map drives. - Check if there are any specific permissions required for mapping the network drives in the script. 2. User Rights Assignment: - In the Group Policy settings, verify that the user has the necessary rights assigned to run scripts. You can check this...
It sounds like you are encountering an issue with mapping network drives via a VBS script after migrating from Windows XP to Windows 7. This issue can sometimes arise due to differences in how user permissions and scripts are handled between the two operating systems. Here are a few troubleshooting steps you can take to resolve this issue: 1. User Permissions: - Ensure that the user account running the script has sufficient permissions to access network resources and map drives. - Check if there are any specific permissions required for mapping the network drives in the script. 2. User Rights Assignment: - In the Group Policy settings, verify that the user has the necessary rights assigned to run scripts. You can check this under "Computer Configuration" > "Policies" > "Windows Settings" > "Security Settings" > "Local Policies" > "User Rights Assignment." 3. Script Execution: - Confirm that the VBS script is compatible with Windows 7. There may be syntax or function differences that affect its execution on Windows 7. - Check the script for any hard-coded paths that might be pointing to incorrect locations on the Windows 7 machine or the network. 4. Network Availability: - Windows 7 may have a different startup sequence compared to Windows XP, which could affect network availability when the script runs during login. - Ensure that the network is fully initialized before the script tries to map the network drives. You might need to introduce a delay in the script to ensure the network is ready. 5. Group Policy Preferences: - Consider using Group Policy Preferences (GPP) to map network drives instead of a VBS script. GPP provides a more flexible and reliable way to manage mapped drives. 6. Event Viewer Logs: - Check the Event Viewer logs on the Windows 7 machine for any errors related to the script execution or network drive mapping. This can provide more insight into what might be causing the issue. By reviewing these aspects and making necessary adjustments to your script and Group Policy settings, you should be able to address the issue of network drives not mapping correctly on Windows 7 after the migration from Windows XP.
 


Solution
Back
Top