rictersmith,
That is the process that we teach our technicians to save bandwidth - however in previous use I believe it has worked for us in the way you are describing where it uninstalls then re-installs without issue.
This is our deployment script - maybe it would help to compare to yours and check for differences:
; This file was generated by Desktop Manager
[MACHINES_NT]
REMEXEC0=MsiExec.exe /q /X{F238CE99-6614-4072-9D20-1D2FA7ED951A}
;{These files installed by OSDRep.msi in the older version
REMCOPY1=%DTMDIR%\landesk\files\bootmenu.1, %LDMS_CLIENT_DIR%\bootmenu.1, TOREMOTE
REMCOPY2=%DTMDIR%\landesk\files\bstrap.0, %LDMS_CLIENT_DIR%\bstrap.0, TOREMOTE
REMCOPY3=%DTMDIR%\landesk\files\dosundi.1, %LDMS_CLIENT_DIR%\dosundi.1, TOREMOTE
REMCOPY4=%DTMDIR%\landesk\vboot\bootmenu.0, %LDMS_CLIENT_DIR%\bootmenu.0, TOREMOTE
REMCOPY5=%DTMDIR%\landesk\vboot\dosundi.0, %LDMS_CLIENT_DIR%\dosundi.0, TOREMOTE
;}
;{These files are needed by winpe2.0 and later
REMCOPY6=%DTMDIR%\landesk\vboot\bcd.dat, %LDMS_CLIENT_DIR%\bcd, TOREMOTE
REMCOPY7=%DTMDIR%\landesk\vboot\bcd_x64.dat, %LDMS_CLIENT_DIR%\bcd_x64, TOREMOTE
REMCOPY8=%DTMDIR%\landesk\vboot\bcd_ia32.dat, %LDMS_CLIENT_DIR%\bcd_ia32, TOREMOTE
REMCOPY9=%DTMDIR%\landesk\vboot\boot.sdi, %LDMS_CLIENT_DIR%\boot.sdi, TOREMOTE
REMCOPY10=%DTMDIR%\landesk\vboot\boot.wim, %LDMS_CLIENT_DIR%\boot.wim, TOREMOTE
REMCOPY11=%DTMDIR%\landesk\vboot\boot_x64.wim, %LDMS_CLIENT_DIR%\boot_x64.wim, TOREMOTE
REMCOPY12=%DTMDIR%\landesk\vboot\bootx64.efi, %LDMS_CLIENT_DIR%\bootx64.0, TOREMOTE
REMCOPY13=%DTMDIR%\landesk\vboot\bootia32.efi, %LDMS_CLIENT_DIR%\bootia32.0, TOREMOTE
REMCOPY14=%DTMDIR%\landesk\vboot\bootmgr.exe, %LDMS_CLIENT_DIR%\bootmgr.exe, TOREMOTE
REMCOPY15=%DTMDIR%\landesk\vboot\pxeboot.0, %LDMS_CLIENT_DIR%\startrom.0, TOREMOTE
;}
REMEXEC16=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /p="http://%CUSTJOBHOSTIP%/landesk/files/osdrep.msi" /msi /N /An /Ac /g="{F238CE99-6614-4072-9D20-1D2FA7ED951A}" /disableclientqueue
REMEXEC17=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /NTT=%CUSTJOBHOSTIP%:5007 /S="%CUSTJOBHOSTIP%" /F /SYNC /NOUI
[MACHINES_95]
SETSTATUS=1240, ERR
[OWNER]
TYPE=OSDOTHERS
I would suggest reviewing a target client after attempting to run your script and see at which point it fails.
1. Does it error when you manually run the uninstall command from line 0, possibly its hanging the script and it never makes it to the install portion?
2. Do any of the file copies fail to make it over?
3. Does it reach line 16 where it does the reinstall?
4. Does line 16 fail when you manually run through the steps above?
Thanks,
Peter