"Always wait for network at computer startup and logon"

[C C]

Is there a Domain policy to enforce this on all WinXP machines?
The default on WinXP of this machine policy is disabled. WinXP
always pretends that everything is alright when the machine
boots up and presents the user with the Logon banner. When
the user logons right away after boot up, he cannot access all
resources that are on the network because XP is doing the
network connection in the background.

I always go around and change the local machine policy to
always wait for network at startup or logon.

Thanks in advance for your help.

[Laura E. Hunter [MVP]]

Yep, it's under Computer Configuration\Administrative Templates\System\Logon

HTH

Laura E. Hunter
Microsoft MVP: Windows Server - Networking
Responses provided as-is, no warranties expressed or implied

Post by C C
Is there a Domain policy to enforce this on all WinXP machines?
The default on WinXP of this machine policy is disabled. WinXP
always pretends that everything is alright when the machine
boots up and presents the user with the Logon banner. When
the user logons right away after boot up, he cannot access all
resources that are on the network because XP is doing the
network connection in the background.
I always go around and change the local machine policy to
always wait for network at startup or logon.
Thanks in advance for your help.

[C C]

Thanks. I know this - to use gpedit.msc in each local machine.
BUT isn't there a DOMAIN Policy to set this to make the
XP machines to wait for network before they present the
logon banner?????

Post by Laura E. Hunter [MVP]
Yep, it's under Computer Configuration\Administrative
Templates\System\Logon
HTH
Laura E. Hunter
Microsoft MVP: Windows Server - Networking
Responses provided as-is, no warranties expressed or implied

Post by C C
Is there a Domain policy to enforce this on all WinXP machines?
The default on WinXP of this machine policy is disabled. WinXP
always pretends that everything is alright when the machine
boots up and presents the user with the Logon banner. When
the user logons right away after boot up, he cannot access all
resources that are on the network because XP is doing the
network connection in the background.
I always go around and change the local machine policy to
always wait for network at startup or logon.
Thanks in advance for your help.

[Doug Sherman [MVP]]

Yes, you can use Group Policy to set this at the domain or appropriate OU
level:

Computer Configuration\Administrative Templates\System\Logon\

Always wait for the network at computer startup and logon

Doug Sherman
MCSE, MCSA, MCP+I, MVP

Post by C C
Is there a Domain policy to enforce this on all WinXP machines?
The default on WinXP of this machine policy is disabled. WinXP
always pretends that everything is alright when the machine
boots up and presents the user with the Logon banner. When
the user logons right away after boot up, he cannot access all
resources that are on the network because XP is doing the
network connection in the background.
I always go around and change the local machine policy to
always wait for network at startup or logon.
Thanks in advance for your help.

[C C]

Thanks. I know how to set at local machine - using gpedit.msc.
BUT how can we set this machine policy at the domain level
so all these WinXP machines will wait for network connection
before letting the user logon???? Thanks in advance.

Post by Doug Sherman [MVP]
Yes, you can use Group Policy to set this at the domain or appropriate OU
Computer Configuration\Administrative Templates\System\Logon\
Always wait for the network at computer startup and logon
Doug Sherman
MCSE, MCSA, MCP+I, MVP

Post by C C
Is there a Domain policy to enforce this on all WinXP machines?
The default on WinXP of this machine policy is disabled. WinXP
always pretends that everything is alright when the machine
boots up and presents the user with the Logon banner. When
the user logons right away after boot up, he cannot access all
resources that are on the network because XP is doing the
network connection in the background.
I always go around and change the local machine policy to
always wait for network at startup or logon.
Thanks in advance for your help.

[Doug Sherman [MVP]]

Open AD Users and Computers, right click the domain or appropriate OU, and
select Properties. Click the Group Policy tab - Edit button.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

Post by C C
Thanks. I know how to set at local machine - using gpedit.msc.
BUT how can we set this machine policy at the domain level
so all these WinXP machines will wait for network connection
before letting the user logon???? Thanks in advance.

Post by Doug Sherman [MVP]
Yes, you can use Group Policy to set this at the domain or appropriate OU
Computer Configuration\Administrative Templates\System\Logon\
Always wait for the network at computer startup and logon
Doug Sherman
MCSE, MCSA, MCP+I, MVP

Post by C C
Is there a Domain policy to enforce this on all WinXP machines?
The default on WinXP of this machine policy is disabled. WinXP
always pretends that everything is alright when the machine
boots up and presents the user with the Logon banner. When
the user logons right away after boot up, he cannot access all
resources that are on the network because XP is doing the
network connection in the background.
I always go around and change the local machine policy to
always wait for network at startup or logon.
Thanks in advance for your help.

[C C]

Doug,

Thanks. But our Win2K AD does not have this option in
the GPO for Administrative Templates->System->Logon->
"Always wait for the network at computer startup and logon".

Is there a way to add this item in the WinwK AD?

Post by Doug Sherman [MVP]
Open AD Users and Computers, right click the domain or appropriate OU, and
select Properties. Click the Group Policy tab - Edit button.
Doug Sherman
MCSE, MCSA, MCP+I, MVP

Post by C C
Thanks. I know how to set at local machine - using gpedit.msc.
BUT how can we set this machine policy at the domain level
so all these WinXP machines will wait for network connection
before letting the user logon???? Thanks in advance.

Post by Doug Sherman [MVP]
Yes, you can use Group Policy to set this at the domain or appropriate

OU

Post by C C

Post by Doug Sherman [MVP]
Computer Configuration\Administrative Templates\System\Logon\
Always wait for the network at computer startup and logon
Doug Sherman
MCSE, MCSA, MCP+I, MVP

Post by C C
Is there a Domain policy to enforce this on all WinXP machines?
The default on WinXP of this machine policy is disabled. WinXP
always pretends that everything is alright when the machine
boots up and presents the user with the Logon banner. When
the user logons right away after boot up, he cannot access all
resources that are on the network because XP is doing the
network connection in the background.
I always go around and change the local machine policy to
always wait for network at startup or logon.
Thanks in advance for your help.

[Ace Fekay [MVP]]

Post by C C
Doug,
Thanks. But our Win2K AD does not have this option in
the GPO for Administrative Templates->System->Logon->
"Always wait for the network at computer startup and logon".
Is there a way to add this item in the WinwK AD?

I believe that's an AD 2003 setting. To create a setting for 2000, it can be
a little tricky and dig up the actual reg entry you want to modify.

323639 - HOW TO Create Custom Administrative Templates in Windows 2000:
http://support.microsoft.com/?id=323639

WindowsDevCenter.com -- Powering Up Administrative Templates:
http://www.windowsdevcenter.com/pub/a/windows/2005/03/08/working_admin_templates.html

Creating Custom ADM Templates - The Lazyadmin.com:
http://thelazyadmin.com/index.php?/archives/125-Creating-Custom-ADM-Templates.html
--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only thing in life is change. Anything more is a blackhole consuming
unnecessary energy. - [Me]

[b***@yahoo.com]

Post by C C
Is there a Domain policy to enforce this on all WinXP machines?
The default on WinXP of this machine policy is disabled. WinXP
always pretends that everything is alright when the machine
boots up and presents the user with the Logon banner. When
the user logons right away after boot up, he cannot access all
resources that are on the network because XP is doing the
network connection in the background.
I always go around and change the local machine policy to
always wait for network at startup or logon.
Thanks in advance for your help.

I have found that if you edit a domain wide group policy that was
created on a Win 2000 server from a Win XP workstation, you will get
all the Win XP settings, and for the most part they will work, even
though they don't show up in the Win 2000 administrative templates. At
a Win XP workstation, you open a new MMC (type "mmc" at the Run command
line) and add the snap-in for Group Policy Object Editor. Then you
will be able to browse to find the domain group policy that you want to
edit. You will find the setting for forcing the workstations to wait
for the network during logon just where the other people described.
The only thing is that when you do this, I think you will find that
whenever you go to edit this GP on the Win 2000 server, it will give
you quite a few error messages complaining that some entries have too
long entries and will be truncated. I never found that this created
problems, but you should probably check with people more knowledgeable
than me before you do this to be sure that there aren't undesirable
side-effects

[Ace Fekay [MVP]]

Post by b***@yahoo.com
I have found that if you edit a domain wide group policy that was
created on a Win 2000 server from a Win XP workstation, you will get
all the Win XP settings, and for the most part they will work, even
though they don't show up in the Win 2000 administrative templates.
At a Win XP workstation, you open a new MMC (type "mmc" at the Run
command line) and add the snap-in for Group Policy Object Editor.
Then you will be able to browse to find the domain group policy that
you want to edit. You will find the setting for forcing the
workstations to wait for the network during logon just where the
other people described. The only thing is that when you do this, I
think you will find that whenever you go to edit this GP on the Win
2000 server, it will give you quite a few error messages complaining
that some entries have too long entries and will be truncated. I
never found that this created problems, but you should probably check
with people more knowledgeable than me before you do this to be sure
that there aren't undesirable side-effects

Tht's something I've never tried. I would assume it would work if you've
already found it to work.

Which adminpak did you install on the XP machine? Win2000 or Win2003?

Ace

[b***@yahoo.com]

I didn't install any admin pak on the XP workstation. The point is to
use the Win XP templates, which are more versatile than the 2000 Server
ones. If you can upgrade that server to Server 2003 SP1, you will get
the same effect without having to go through the XP workstation,
because the templates on 2003 SP1 are almost the same as on Win XP. I
assume that you haven't upgraded that 2000 Server machine for a reason.
If there is no reason not to upgrade, and you use Group Policy for a
lot of your workstation configuration, you will like the 2003 Group
Policy templates. The Office 2003 templates are also neat, and I use
them alot to configure Office options.

Post by Ace Fekay [MVP]

Post by b***@yahoo.com
I have found that if you edit a domain wide group policy that was
created on a Win 2000 server from a Win XP workstation, you will get
all the Win XP settings, and for the most part they will work, even
though they don't show up in the Win 2000 administrative templates.
At a Win XP workstation, you open a new MMC (type "mmc" at the Run
command line) and add the snap-in for Group Policy Object Editor.
Then you will be able to browse to find the domain group policy that
you want to edit. You will find the setting for forcing the
workstations to wait for the network during logon just where the
other people described. The only thing is that when you do this, I
think you will find that whenever you go to edit this GP on the Win
2000 server, it will give you quite a few error messages complaining
that some entries have too long entries and will be truncated. I
never found that this created problems, but you should probably check
with people more knowledgeable than me before you do this to be sure
that there aren't undesirable side-effects

Tht's something I've never tried. I would assume it would work if you've
already found it to work.
Which adminpak did you install on the XP machine? Win2000 or Win2003?
Ace

[Ace Fekay [MVP]]

Post by b***@yahoo.com
I didn't install any admin pak on the XP workstation. The point is
to use the Win XP templates, which are more versatile than the 2000
Server ones. If you can upgrade that server to Server 2003 SP1, you
will get the same effect without having to go through the XP
workstation, because the templates on 2003 SP1 are almost the same as
on Win XP. I assume that you haven't upgraded that 2000 Server
machine for a reason. If there is no reason not to upgrade, and you
use Group Policy for a lot of your workstation configuration, you
will like the 2003 Group Policy templates. The Office 2003 templates
are also neat, and I use them alot to configure Office options.

Good way to do it. I hope it helps the original poster.

Ace