klyptix
asked on
DFS Mapping through Script Hit or Miss Kixtart
Good Evening Everyone,
We recently enabled DFS Sharing creating two roots on a Windows 2003 R2 SP2 Server in a domian. Each root contains links to various other mappings on the same server. We chose to use DFS for organizational purposes. The data is too large to replicate therefore we don't.
Through the use of a login script ... kixtart to be exact, the users OU in AD is discovered and they are mapped accordingly to their DFS root. We are moving away from Kixtart soon to a pure VB script applied via GPO. I have attached snipits of code to this article.
Should we be mapping to \\domain.local\root or \\server.domain.local\root where server is the dfs server? Sometimes the users get the mapping, other times they don't get anything. They can log off and log back in and the status may change, it may not. They may log out when they have the drive to see when they return it is gone. They may log in to no mapping, log off, come back and it's there. This leads me to believe it is not a permissions issue.
They get their home drive which is mapped through their domain profile. I am fairly sure that the script runs regardless of the status of the "G:" drive.
Perhaps the issues will go away when we switch to the VB script. Perhaps its a limitation of Kixtart. Any guidance will be greatly appreciated. :) My staff, students, and colleagues thank you in advance for your assistance.
EDIT: The clients are all Windows XP. Issues happen regardless of the users OU.
We recently enabled DFS Sharing creating two roots on a Windows 2003 R2 SP2 Server in a domian. Each root contains links to various other mappings on the same server. We chose to use DFS for organizational purposes. The data is too large to replicate therefore we don't.
Through the use of a login script ... kixtart to be exact, the users OU in AD is discovered and they are mapped accordingly to their DFS root. We are moving away from Kixtart soon to a pure VB script applied via GPO. I have attached snipits of code to this article.
Should we be mapping to \\domain.local\root or \\server.domain.local\root
They get their home drive which is mapped through their domain profile. I am fairly sure that the script runs regardless of the status of the "G:" drive.
Perhaps the issues will go away when we switch to the VB script. Perhaps its a limitation of Kixtart. Any guidance will be greatly appreciated. :) My staff, students, and colleagues thank you in advance for your assistance.
EDIT: The clients are all Windows XP. Issues happen regardless of the users OU.
Kixtart Script Snipit
Case InGroup( "All Staff" )
Use G: /delete
Use G: "\\server.domain.local\Faculty"
Label ( 'G:\' , 'Shared Drive' )
Case 1
Use G: /delete
Use G: "\\server.domain.local\Students"
Label ( 'G:\' , 'Shared Drive' )
VB Script Snipit - this is not live yet.
strOUPath = objUser.Parent
arrContainers = Split(strOUPath, ",")
arrOU = Split(arrContainers(0), "=")
strOU = arrOU(1)
If strOU = "Staff" Then
strDrive = sharedPathFaculty
Else
strDrive = sharedPathStudents
End If
' Map Group drive
objNetwork.RemoveNetworkDrive sharedDriveLetter
objNetwork.MapNetworkDrive sharedDriveLetter, strDrive
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER