2006
05.12

We are going through a Groupwise to Exchange conversion right now and of course their are a thousand hoops to jump through every step of the way. The latest challenge is that all the Groupwise mailboxes need to give proxy access to the user that will be running the migration. This means that every mailbox has to be touched since Groupwise doesn’t allow for a global proxy addition to all mailboxes. After gleaning a lot of info from the internet, I ended up writing this visual basic script that will do the job nicely from a login script:

’Link to the Groupwise Object API
Set GWApp = CreateObject("NovellGroupWareSession")
Set fso = CreateObject("Scripting.FileSystemObject")

’Login to Groupwise
Set GWAccount = GWApp.Login()

’Check if we’ve already run
If fso.FileExists("\\fileserver\temp\path\" & GWAccount.Owner.EmailAddress & ".tmp") Then
  WScript.echo "Already ran.  Quitting!"
  GWApp.Quit
  WScript.Quit
End If

’Find the account you want to add to the proxy list from the Global 
Address Book
Set GWEntry = GWAccount.SystemAddressBook.AddressBookEntries.Find("(<last Name> CONTAINS ""Migrator"")")
Set GWAddress = GWEntry.Item(1)

&#8217;Add the account as a proxy
call GWAccount.AccountRights.Add(GWAddress, 65535)
call GWAccount.Refresh

&#8217;Touch a file to let us know things ran well
Set ngwFile = fso.CreateTextFile("\\fileserver\temp\path\" & GWAccount.Owner.EmailAddress & ".tmp", True)
ngwFile.WriteLine("Archive " & GWAccount.Owner.EmailAddress & " " & GWAccount.DefaultPathToArchive)
ngwFile.Close
 
&#8217;Finish
GWApp.Quit

It uses the Groupwise Object API. We created a Groupwise account called “Groupwise Migrator” to run the migration wizard with but you can put anyone’s last name in their that you want to add as a proxy. We also touch a temp file just so we don’t run twice on the same machine. Run it early on after the user boots up so their is little chance that they might already be proxied into someone’s box. Enjoy!

No Comment.

Add Your Comment

Switch to our mobile site