You're still actively on that drive when you're trying to delete it. You
really can't delete your PWD. You need to get off the T: drive first and then
it should delete correctly. If you were actually watching this run you'd get
the "there are still open files.... " message in your script which it doesn't
know how to handle.
The easiest way will be to do a pushd t: instead of just changing to t:, then
do a popd after you're done, then delete the drive. I've also found that
sometimes you have to actually some action from the command line in order to
get the connection to release. A simple dir command will handle that.
All this said, is there any requirement that you run the executable from t:?
Perhaps just providing the path to it would be enough. In that case your
script would work correctly without the extra gyrations.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of J- P
Sent: Friday, January 2, 2015 10:27 PM
To: NT
Subject: RE: [NTSysADM] EXE to MSI-help
didnt work, still shows in explorer with red X
II appreciate the suggestion, i'll just have them reboot
Jean-Paul Natola
________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] EXE to MSI-help
Date: Sat, 3 Jan 2015 03:03:05 +0000
Have it tried it with:
net use t:
\\SERVER\software\Vectorworks\Vectorworks2015-SP2-SeriesB-win<file:///\\SERVER\software\Vectorworks\Vectorworks2015-SP2-SeriesB-win>
/persistent:no
Thanks
Webster
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of J- P
Sent: Friday, January 02, 2015 8:53 PM
To: NT
Subject: RE: [NTSysADM] EXE to MSI-help
So here is my butchering of a script, the issue I'm having is the that T: drive
remains in explorer till the second reboot (when the script just goes to END)
Any feedback is greatly appreciated
if exist "C:\Program Files\Vectorworks2015" goto END
net use t:
\\SERVER\software\Vectorworks\Vectorworks2015-SP2-SeriesB-win<file:///\\SERVER\software\Vectorworks\Vectorworks2015-SP2-SeriesB-win>
t:
installvectorworks.exe -q -u "USER" -c "Company Name" -s
serial-number-of-product -d "C:\Program Files\Vectorworks2015"
net use t: /delete
:END
tia
________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] EXE to MSI
Date: Thu, 1 Jan 2015 22:03:41 +0000
+1
As long as the EXE install is "silent", it should work fine.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: Thursday, January 1, 2015 5:01 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [NTSysADM] EXE to MSI
I'd do it with a script, personally, depending on environment size and
infrastructure tools available.
GP startup script would be ideal, in the absence of anything that would make
life easier
Sent from my BlackBerry(r) smartphone on O2
________________________________
From: J- P <[email protected]<mailto:[email protected]>>
Sender: [email protected]<mailto:[email protected]>
Date: Thu, 1 Jan 2015 11:48:10 -0500
To: NT<[email protected]<mailto:[email protected]>>
ReplyTo: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] EXE to MSI
Hi all and Happy New year.
It's been a while since I had to push out an EXE app (as most now come with
MSI), anyhow this vendor is still stuck a few decades behind ;)
I vaguely recall having an application that converted EXE to MSI, but cant
remember it for the life of me.
What do most people do/use to deploy an executable?
Thanks
