Jim
Tue Jul 05 15:17:54 CDT 2005
Why not use the AD replication monitor tool, you can push or pull AD
updates.
See
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/691910f2-a6a7-4ced-984e-972aec2cbdd2.mspx
"Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
news:Oh1HA8$dFHA.3712@TK2MSFTNGP12.phx.gbl...
> Thanks for the input. I had already set the replication to 15 minutes. I
> have been using the AD Sites and Services to manually force replication
> but
> just wanted to give our Help Desk an easier way. Thanks for your input.
>
>
> Fred
>
>
>
>
>
> "BCE" <dirwolf@speakeasy.net> wrote in message
> news:e2yKWZ5dFHA.2664@TK2MSFTNGP15.phx.gbl...
>> If your network utilization is that low, decrease your replication times
> on
>> your site links, I support a large ad infrastructure across 3 continents
> and
>> we use 15 minute replication intervals.
>> You can also control which GC's you exchange systems are talking to by
>> hardcoding the systems in system manager, you can then instruct your help
>> desk to only use those two systems when creating a mailbox.
>> If you have distributed exchange servers, you can still do that with a
>> little work.
>>
>> This script we created off a microsoft script, be sure to read the
> comments,
>> you need add your domain names where the dc=?values are missing.
>>
> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
> ''''
>> ' SYNCDC.vbs
>>
> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
> ''''
>> ' Version 1.1
>> ' Script forces replication between 2 domain controllers - the TARGET
> server
>> ' pulling information from the SOURCE server, provided an AD connector
> links
>> ' them directly.
>> '
>> ' This script can only be run on a Windows 2000 PC with the Windows 2000
>> Support
>> ' Tools installed (found in the SUPPORT\TOOLS directory of the W2K Server
>> CD)
>> ' and relies on IADsTools.DLL
>> '
>> '
>>
> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
> ''''
>> ' Changes:
>> '
>> ' 1.1 Added target server name to success/failure message.
>> '
>>
> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
> ''''
>> Dim strTargetServer
>> Dim strSourceServer
>> Dim Result
>> Dim comDLL
>> Dim iReplErr
>> '
>> ' Initialize the error flag
>> '
>> iReplErr = 0
>> '
>> ' Requests source and target server names (both default to SEUKG-GC001)
>> '
>> strSourceServer = InputBox("Enter Source Server (Server to pull changes
>> from)", "Source Server?", "ENTER SOURCE SERVER NAME HERE")
>> strTargetServer = InputBox("Enter Target Server (Server to be updated)",
>> "Target Server?", "ENTER DESTINATION SERVER NAME HERE")
>> '
>> ' Creates AD object
>> '
>> Set comDLL=Createobject("IADsTools.DCFunctions")
>> '
>> ' Calls the subroutine to synchronize the Domain, Config and Schema
>> partitions
>> '
>> 'YOU NEED TO FILL IN THE MISSING PIECES BELOW
>> '1ST LINE IS YOUR DOMAIN
>> Call SyncPart("DC=,DC=,DC=", strSourceServer, strTargetServer, sDomMsg,
>> iReplErr)
>> '2ND AND 3RD LINE IS FOR ROOT DOMAIN
>> Call SyncPart("CN=Configuration,DC=,DC=", strSourceServer,
> strTargetServer,
>> sConfMsg, iReplErr)
>> Call SyncPart("CN=Schema,CN=Configuration,DC=,DC=", strSourceServer,
>> strTargetServer, sSchemaMsg, iReplErr)
>> '
>> ' Depending on replication success displays a status message
>> '
>> If iReplErr = 0 Then
>> iRetCode = MsgBox (sDomMsg & VbCrLf & sConfMsg & VbCrLf & sSchemaMsg,
>> vbInformation, "Replication to " & strTargetServer & " Successful")
>> Else
>> iRetCode = MsgBox (sDomMsg & VbCrLf & sConfMsg & VbCrLf & sSchemaMsg,
>> vbExclamation, "Replication to " & strTargetServer & " Failed")
>> End If
>>
>> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>> ' #### End of Main Program - Functions & Subroutines Follow
>> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>> Sub SyncPart(xPart, xSrc, xTrgt, xMsg, xReplErr)
>> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>> ' Triggers replication of appropriate partition with source server
>> ' and returns either success messsage or error text
>> '
>> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>> Result=comDLL.ReplicaSync(Cstr(xTrgt), CStr(xPart), CStr(xSrc))
>> If Result=-1 Then
>> xMsg = "Failed to replicate partition " & xPart & " : " &
>> comDLL.LastErrorText
>> xReplErr = 1
>> Else
>> xMsg = "Partition " & xPart & " replicated successfully."
>> End if
>> End Sub
>>
>>
>> --
>> BRIAN EDWARDO
>> brianedwardo@email.uophx.com
>> arp421-aol
>> dirwolf@msn.com-msn messenger
>> "Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
>> news:ev93DB2dFHA.580@TK2MSFTNGP15.phx.gbl...
>> > Al,
>> >
>> > Our network utilization runs less than 2% so performing AD replication
> has
>> > virtually no
>> > effect on our users. I see your point but never the less, I need a
> script
>> > that will allow
>> > me to replicate AD using a script.
>> >
>> >
>> > Thanks,
>> > Fred
>> >
>> >
>> >
>> > "Al Dunbar [MS-MVP]" <alan-no-drub-spam@hotmail.com> wrote in message
>> > news:uRMld41dFHA.2520@TK2MSFTNGP09.phx.gbl...
>> >>
>> >> "Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
>> >> news:%23H$byY1dFHA.3012@tk2msftngp13.phx.gbl...
>> >> > I need to have an easy way for our Help Desk to initiate AD
>> >> > replication.
>> >> > Thus far I have been unable to find any script that will do this.
> When
>> >> our
>> >> > Help Desk creates new Exchange Mailboxes it sometimes takes 30
> minutes
>> > or
>> >> so
>> >> > for things to show up. Ideally, I would like to just give our Help
>> >> > Desk
>> >> > users a VBS script to run from their desktop that would initiate AD
>> >> > replication on demand.
>> >>
>> >> Our wait can be up to an hour, and we manage to live with that. Hey,
>> >> if
>> > the
>> >> not-yet-a-user was *that* anxious to start sending and receiving
> e-mail,
>> > he
>> >> would have contacted us an hour earlier. ;-)
>> >>
>> >> But seriously, why tinker with something that works? Replication
> traffic
>> > is
>> >> tough enough on the network when it runs on its own schedule - how
>> >> much
>> >> worse would it be to force it whenever an admin or a help desk person
>> > makes
>> >> a change they would like to have take place instantaneously?
>> >>
>> >> /Al
>> >>
>> >>
>> >
>> >
>>
>>
>
>