Re: Computer Can't Access Installation Source For Assigned Package
From: Ade (q2k0sde02@sneakemail.com)
Date: 01/20/03
- Next message: Gousigan: "Will anybody help me?"
- Previous message: Mike B.: "How to script enable file auditing"
- In reply to: Ade: "Computer Can't Access Installation Source For Assigned Package"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Ade" <q2k0sde02@sneakemail.com> Date: Mon, 20 Jan 2003 12:02:41 -0000
Looks like my problem was because I added the packages to the group policy
using \\alias\share as the source of the installation point rather than
using the server's real name. According to
http://support.microsoft.com/default.aspx?scid=kb;en-us;281308, if you
install W2K SP3 and add DisableStrictNameChecking=1 to the LANMANServer
(Server Service) parameters registry key then aliases should work, but
obviously this is not true in all cases.
Does anyone know how to tweak this service to allow aliases to work when
installing packages assigned to computers with group policies?
Thanks,
Ade.
"Ade" <q2k0sde02@sneakemail.com> wrote in message
news:3e270a81$0$239$ed9e5944@reading.news.pipex.net...
> I'm having a problem getting an assigned package to install at computer
> startup. The assignment succeeds, but when the Windows Installer comes to
> access the share containing the software I get the following error in
event
> log (returns status code 1612):
> "Failed to apply changes to software installation settings. Software
> changes could not be applied. A previous log entry with details should
> exist. The error was The installation source for this product is not
> available. Verify that the source exists and that you can access it."
>
> I've created an administrative installation point, created a package for
the
> software in the computer configuration part of the group policy on the top
> level OU, created a global group for computers which use this particular
> package and given this group 'read' and 'apply group policy' permissions
on
> the group policy itself. I've also given Domain Computers full control
> access to the share and files in the administrative installation point.
>
> I've noticed that if I give the computer in question (let's call it TEMP)
> direct access to the share and files, after a while is looks like a user
> called TEMP$ (its icon changes from a computer to a user) in the
> Security/Properties box.
>
> I can install the software from the administrative installation point
> manually after a user logs in, or by creating the group policy in the user
> configuration part of a group policy. So the package itself is fine.
>
> Can someone help suggest why this isn't working?!
>
> Thanks,
>
> Ade.
>
>
>
>
- Next message: Gousigan: "Will anybody help me?"
- Previous message: Mike B.: "How to script enable file auditing"
- In reply to: Ade: "Computer Can't Access Installation Source For Assigned Package"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
