Group Renaming on AD and NT4
Novell Cool Solutions: Trench
By Peter Van Andel
|
Digg This -
Slashdot This
Posted: 29 Jun 2004 |
Posted: 29 Jun 2004
The Problem
Renaming an NDS group caused problems in the synchronization of this group on AD and NT4 platforms.
The Solution
Changed parts of the rename.wsf platform receiver scripts on NT4 and AD.
Changes in the rename.wsf script on AD:
'/ Commented out the following line
'/ set adsUser = adsContainer.GetObject("user", newname)
if WshShell.ExpandEnvironmentStrings("%objectClass%") = "ASAM-platformUser" then
'/ Added the following line
set adsUser = adsContainer.GetObject("user", newname)
adsUser.UserPrincipalName = adsname
adsUser.samAccountName = WshShell.ExpandEnvironmentStrings("%samAccountName%")
else
'/ Added the following line
set adsUser = adsContainer.GetObject("group", newname)
adsUser.samAccountName = adsname
end if
adsUser.SetInfo
Changes in the rename.wsf script on NT4:
'/ Added the following line
if containerType = "cn=users" then
set adsUser = adsContainer.GetObject("user", oldname)
'/ Added the three following lines
else
set adsUser = adsContainer.GetObject("group", oldname)
end if
If you have questions for Peter about this solution, you can contact him at p.j.g.van_andel@TAKETHISOUTlumc.nl
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com