Re: Deploy office 2003 to XP workstations

Hi Mark,

I enabled the policy GPO using GPMC, I'm able to see the setting. Then I did
gpupdate /force, rebooted it, I can see the logon window right away, the
software wasn't installed. The way I deploy the office2003 is that created a
package in computer configuration, then move a few workstations into this
OU. Anything I'm still missing? BTW, I'm using a laptop to do this test.
Would laptop work with this policy?

Thanks again,
Sarah
"Mark Heitbrink [MVP]" <spam-only@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OaM7dHkiGHA.1600@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

Sarah schrieb:
I'm new to group policy, and I did read your posting carefully and went
to group policy to look where is the setting. And I'm still confused.

Sorry, I thaught the "technic" was familiar to you, because deploying
Office with a GPO is perhaps Step 7 or 8 after playing a lot around with
GPOs and manipulation the the registry with the Administrative Templates.

Thats why I just posted the policy, which one you should activate.

I don't quite understand what to do with "Always wait for the network at
computer startup and logon." Does this has to be done on AD GPO?

Yes. Just activate it.
The recommended thing is using the GPMC from MS to work with GPOs.
Inside a 2K GPO you will not see this setting, you need a XP or 2003
from where you edit setting.

XP works with a asynchronous startup behavior. This is a "trick" to show
the user the desktop really fast, but in the backround a lot of services
and drivers are not started. They start later than the explorer.exe
People "feel" like having a much more faster OS ...

The problem is: The network driver starts to late. XP logs you on with
cached credentials, e.g. logon scripts run only after log off and log on
again, software deployment during startup will fail, because the network
isn´t ready.

If you activate the policy, it is doing what it say:
"Always wait for the network ..."
Now, after applying this setting, XP laods the networkdrivers during
startup and the software can be deployed.

As an alternative, you can set "Run login scripts synchronously".
This setting has 2 positiv effects:
- the network drivers load during startup, so it´s the same efect like
"alway wait for the network"
- the explorer.exe loads after all login scripts have run.

the Scripts are sycronized, they start one after the other in the end
the explorer starts. This setting can be applied to 2000 clients aswell,
(even NT4 know this setting with system policies).

e.g. If a user has linked some programs to his \startmenu\startup and this
program need a mapped drive or something similar, then you can prevent
errors with activating the "run scripts sync" policy, because the
mapped drives an all connections or other settings that you define
in your login script have been done. The explorer.exe and so the startup
starts after all scripts.

I always activate "run scripts sync" in every network, to get control over
the start sequence (which script runs first and when all settings done,
the user can get his explorer and start his work).
Aswell with this setting I don´t need to activate "Always wait for the
network" because with this the XP Startup is no longer asynchronous.

Mark
--
Mark Heitbrink - MVP Windows Server
Homepage: www.gruppenrichtlinien.de
extend GPO: www.desktopstandard.com
PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.


.

Relevant Pages

  • Re: Logon Scripts Acrossed VPN
    ... This error looks specific to the computer account rather than user account and I'm guessing its related to GP computer processing firing off before the network to the DC is available. ... Group Policy processing aborted. ... Scripts are a pain the you-know-what to troubleshoot but here are a few ...
    (microsoft.public.windows.group_policy)
  • Re: Deploy office 2003 to XP workstations
    ... Does this has to be done on AD GPO? ... XP works with a asynchronous startup behavior. ... The network driver starts to late. ... you can set "Run login scripts synchronously". ...
    (microsoft.public.windows.group_policy)
  • Re: Cached GPOs
    ... seen to caching occurs when you're editing a GPO. ... Template policy to ... > It may have been that at one time when the users were off network they ... >>> would still have the screen saver tab hidden because none ...
    (microsoft.public.windows.group_policy)
  • Re: EventID 1054 from Userenv for startup script
    ... This order means that the local GPO is processed first, and GPOs that are linked to the organizational unit of which the computer or user is a direct member are processed last, which overwrites settings in the earlier GPOs if there are conflicts. ... So if you said "some machines don't have full access to the network at startup" the GPO's seems not to apply correct. ... in the right window "Group policy Inheritance tab", ... The startup script is applied to the computer, ...
    (microsoft.public.windows.group_policy)
  • Re: pushprinterconnection.exe
    ... Just to verify, did you use the startup scripts, or did you use logon ... the location on the network that your policy points to (the ... Does GPO deployment work under that scenario? ...
    (microsoft.public.windows.group_policy)