Files to Private Network Shares

[JXBURNS]

Logged on as Domain Administrator.

Install$ is a private network share for \\SHIPSERVER\APPS\InstallationSource. APPS is a public share.

%InstallerSource% = \\SHIPSERVER\Install$\TankerLoading
[Set in Session Variables]
Installing one file (filename.MSI) from Archive tab to %InstallerSource% reports decompression error #5 and 'could not open output file'.

Change the destination to be:
%InstallerSource% = \\SHIPSERVER\APPS\InstallationSource\TankerLoading

Works fine. I know it works OK with public shares but seems to not like the private version.

As an aside, I had to click IGNORE to bypass the error however the log file reported SUCCESS installing the file (it did not install) but no sign of the original error. Should not every error be logged (Extended Errors is on)?

Any ideas?

Thanks - John

[AxemanMK]

Are you installing a file TO the private share, or FROM the private share ??

Either way, you might want to check the "SHARE PERMISSIONS" of the $ share. Even though you are a Domain Admin, the share permissions might not be open enough for you to complete your task.

[JXBURNS]

I was about to say "don't be silly" of course it is set to Full Control for Everyone but luckily did not open my mouth before checking. Sure enough the private share was set to read only for Everyone. Worst still there should have been a Domain Admin entry with Full control but looks like somehow someone managed to delete it probably by deleting/recreating the share.

"Honest guv, wasn't me!" I can hear my colleagues saying:)

Thanks for suggestion - of course it now works....

Rgds John

[AxemanMK]

LOL.... Yer very welcome.

Oh, by the way........ Just wait till you start working on Vista !!!
Its a nightmare !!..... With UAC on, a mapped drive exists. Great.

But when you launch an installer across a network connection, and it
wants ADMIN privilages, the install WONT see the mapped network drive
because the process has been elevated to administrator, by way of
RUNAS.... So obviously, the mapped network drives wont exist.

Its driving me nuts !!!

[JXBURNS]

Been there with Vista already - took me twice as long to install a network compared to the same thing on XP for the same reasons you mention amongst others. Personally I will stick with XP for time being as I see little advantage when it takes so much more time to carry out a simple task. I understand what they are trying to do but I already lock down our systems through judicious use of group policy. A user cannot even get to the RUN command which is a major way to stop people fiddling.

Will let Vista get to Service Pack 1 first!

John