Wednesday, December 2, 2009

ZENWorks Device should re-register itself with the zone with a new GUID

1. zac unr (should remove the device object from the zone)
2. zac fsg -d (deletes the GUID)
3. clear image safe data using ziswin - save the settings, don't set
the "just imaged flag"
4. deleted devicedata and deviceguid from c:\program
files\novell\zenworks\conf
5. If C:\Program Files\Novell\ZENworks\Conf\Guid.txt exists, delete it
6. Delete the directory "C:\Program Files\Novell\ZENworks\Cache\zmd"
7. rename "C:\Program
Files\Novell\ZENworks\Conf\initial-web-service.bak" to
"initial-web-service"
8. Reboot - (Device should re-register itself with the zone with a new
GUID)

Thursday, November 19, 2009

extract files from a .msi file using the Windows command line

Every once in a while I need to extract the content of a .msi file in order to customize a deployment for a particular network environment. Sometimes initializing the .msi installer will temporarily extract the files into C:\Documents and Settings\<username>\Local Settings\Temp, but those files are removed once the installer exits.

To extract files from a .msi file at the command line, type:

msiexec /a PathToMSIFile /qb TARGETDIR=DirectoryToExtractTo

For example, to extract files from f:\zenworks\zfdagent.msi into c:\zfd701 you would type:

msiexec /a f:\zenworks\zfdagent.msi /qb TARGETDIR=c:\zfd701

The destination directory does not need to exist prior to running this command.