General discussion

Locked

XP Service Pack 2 Deployment

By taz1nl ·
Hi All,

I'm currently trying to deploy xp sp2 via AD but am having problems. I performed the following steps:

1. downloaded xp sp2 (for network installations)from microsoft and created a directory on my local C: drive to extract the files to.

2. created a network share (distribution point)for the update.msi file. This share was created on a DFS.

But when I get around to running the admin install I get an error 'This installation package could not be opened. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package'. I looked up the error on the net and it seems to point at insufficient access to the installation folder (which I assume is the distribution folder I created on the DFS). The folder on my local drive where I extracted the files has everyone full control, and on the DFS I have authenticated and domain users read/execute and domain admins full control. I am logged in as domain admin myself.
I have xp sp2 installed on my pc so the windows installer version should be ok. Furthermore, microsoft provide this syntax for admin installs for xp sp2 which seems to be incorrect:

\msiexec /a \\servername\sharedfolder\update.msi

I have tried everything I can think of so far but keep getting the same error. Is there something I'm missing out?

Any help would be welcome!

Thanks,

Taz

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by ReWrite In reply to XP Service Pack 2 Deploym ...

Are you in the \i386\update directory where you extracted the service pack files to when you run the command?

Cheers.

RW

Collapse -

by taz1nl In reply to XP Service Pack 2 Deploym ...

Hi,

Yes, I am but I get the same error. On the MS newsgroups one system admin had suggested this:

1. extract SP files directly to the target distribution folder.

2. Create the GPO for Computer settings and point the GPO to the \\server\<yourfolder>\update\update.msi

he says it should still work that way, because basically the only thing you need is an unpacked SP and the update.msi installer package. The reference to \\Server\SharedFolder\Update.msi should at least read:
\\Server\SharedFolder\i386\update\Update.msi because there is no such thing
as a update.msi package at the referenced location, so the error you're
getting (Could not open package) is justified.
Or \\Server\SharedFolder\update\Update.msi if you make the i386 the sharepoint.

I tried the above and this has worked, so it looks like the documentation on the MS site is not correct! However, will I get any problems in future after deployment of XP SP2 since there was no admin install per se? I ask this because later on I'm going to need to apply updates/patches to the SP as and when they appear. Please advise.

Thanks,

Taz.

Collapse -

by sgt_shultz In reply to XP Service Pack 2 Deploym ...

no problems expected due to your method of installation. way to go. first thing to do with any error message is take it a face value, yes?

Back to Networks Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums