in-line....
-----Original Message-----
Hi Cary,
Thanks for the post.
I have done everything as they are mentioned in all the helps that I
have found to no vail.
1. I created a network share on my server
so, you have \\servername\sharename. Perfect!
2. Shared with Everyone Read & Execute rights
Replace "Everyone" with "Domain Computers". "Everyone" is
far too much. This GPO is being assigned to the computer
accounts so there is no need for users to have any
permissions at all to it. In fact, I would even share it
as "sharename$" - so that it does not appear at all when
tusers are browsing...with the "$" being the key to that.
Also, please please please remember that there are two
sets of permissions involved - the SHARE Permissions and
then the NTFS ( aka Security ) Permissions.
3. Placed the I386 folder to that share
Is this the extracted I386 folder? And from where do you
have this I386 folder?
Okay, that will work for testing. When you really do it I
would create an OU Called PCs and then create a sub-OU
called WIN2000 and another sub-OU called WINXP Pro. So,
it would look like this:
PCs
WIN2000
WINXP Pro
5. Placed my computer on that OU
Perfect...when you really deploy this though I would
assign the GPO to either the WIN2000 sub-OU and to the
WINXP Pro sub-OU. Just make sure to put the machine
accounts in the appropriate sub-OU....
6. Created a group to which apply the Testing GPO
Security groups have absolutely nothing to do with
applying GPOs - other than to filter to which accounts the
GPO should apply. By default, the "Authenticated Users"
group has the "Read" and "Apply Group Policy" permissions
to all GPOs ( well,... ). The only need for creating a
security group would be if you were going to place
whatever accounts ( either user or computer - in this case
computer ) in that particular security group, remove
the "Authenticated Users" group from the Permissions and
replace it with the one you created. In this particular
situation I do not see a need to do this...
In your post you simply stated that you created a
group....what did you do with this group? Did you put the
computer account in that group? Where did you create this
group? inside the Testing OU? inside the Users container?
inside the Computers container?
7. Opened the OU's GPO and made a new one
Good, so you right-clicked the OU ( in your case, TESTING -
in the example that I gave above you would do this for
both the WIN2000 and the WINXP Pro sub-OUs ) and selected
Properties and then went to the Group Policy tab and
selected NEW...
8. Under Computer configuration - SOftware installation I created a
new package (Assigned)
Perfect...you can only assign GPOs to the computer
configuration. When applying GPOs to the user
configuration you can either assign or publish ( and do
not forget about the ADVANCED option. This is very
important when using .mst files...say, for example, with
Office 2000 or Office XP ).
9. I DID not browse the msi file. I wrote the UNC name to
that
So, the UNC Path that you entered would look something
like "\\servername\sharename\i386\update\update.msi"
If I were you, I would restart the computer to which you
want the GPO applied and see what happens. I have noticed
that if you do not give it enough time ( have fun figuring
out how much time is enough! ) it will not work
sometimes. Give it a few more minutes and then reboot and
it works!
However, if it still does not work, I would take a look at
the path. I would actually "browse" to the .msi file by
first entering "\\servername" as this will give a list of
all the shares on this server. I would then manually
enter "\sharename" as this will give you a list of all the
folders and files inside that "sharename". I would then
manually enter "\i386" and then manually enter "\update"
and then manually enter "\update.msi"...You should have it
with this...Naturally, if you have a different path then
you would need to enter that path. The path that I am
using is the path that I have used a hundred times...
10. I rebooted my computer
As you are supposed to...
11. It says about 3 seconds that "installing Managed
SP3 ...."
Like it usually does...
What do you mean? Have you gone to My Computer, right-
clicked and selected Properties. What does it say on the
General Tab?
What you are experiencing is generally a permissions
problem. I suspect that either it has something to do
with the group that you created or it could also be that
you entered "update.exe" instead of "update.msi"???
Do you see any event log entries? You could also install
GPOTOOL and GPRESULT on this computer and let us know what
the output is...
What am I doing wrong`????
TIA,
Markus
GPO.
It always
Markus,
In addition, you need to use the UNC path instead of a
mapped network drive. So, the path to update.msi needs to
be something like \\servername\sharename\i386
\update\update.msi as opposed to F:\sharename\i386
\update\update.msi and you need to make sure that the
group Domain Computers has at least read permissions (
both Share and NTFS ) to this folder...
HTH,
Cary
.
[/QUOTE]
