Batch or automatic server name change in EG projects after upgrade

[nwelke]

Hi all,

We are building a new environment with 9.2 to replace an old 9.2 environment that had been an upgrade of 9.1.  The old environment had its compute server defined as SASMain.  The new one is SASApp. 

Is there an automated or programmatic way to change users' EG projects to reference SASApp instead of SASMain?  So far we're having to open each project and change the assigned server, then save.  This is not a problem for users with a handful of projects but we have a couple departments with hundreds of projects per user.

Any suggestions?

TIA

Nick

[AngelaHall · Accepted solution]

Hi Nick!

Does the Migration Utility not work for this scenario since it's going from 9.2 to 9.2?

Here are my two blog posts about how the Enterprise Guide and Add-in to MS Office Migration Utility work (from 9.1.3 to 9.2):

http://blogs.sas.com/content/bi/2009/10/01/migration-utility-for-eg-4-2-and-add-in-to-ms-office-part...

http://blogs.sas.com/content/bi/2009/10/02/migration-utility-for-eg-4-2-and-add-in-to-ms-office-part...

~ Angela Hall

[nwelke]

Hi Angela - thanks for this, I hadn't realized there was a migration utility for EG.  I'll check if it will fix our server mismatch even though it's the same version of SAS.

Nick

[AngelaHall]

Let me know if it works!

~ Angela (continuously curious)

[nwelke]

FYI, it does work - the wizard converts succesfully from 4.2 to 4.3 and makes the requisite changes.  The only snag we ran into was that running it across multiple machines required setting up a mapped drive because it wouldn't work with UNC paths.  Batch file below:

@echo off

title Starting EG Migration Wizard

color 02

cls

net use s: \\10.20.30.40\sasdepot92m3

s:

cd

pause

echo   Migration Wizard Running...

color 0c

"%programfiles%\SAS\EnterpriseGuide\4.2\MigrationWizard.exe" "s:\__my_migration_record.mig"

color 02

echo   Migration Wizard Finished...

title Migration Wizard Finished

c:

net use s: /d

pause