SP2 'NET USE /HOME' bug ??

[Brian Steele]

Hi Everyone:

After installing SP2 on a few PCs in the office, we
discovered that several of them would suddenly crash and
reboot after certain users logged in. This did not happen
when the PCs were at SP1, and the problem appeared to be
happening only with users that did not have administrative
level access on their PCs.

Each account in our AD is configured to run a script after
logging on. I traced the problem down to the PCs in
question executing the following command in the logon
script:

NET USE (driveletter): /HOME /N


If that command is executed from the command prompt, the
PC bugchecks and reboots. This problem does not happen
however if the logged account has administrative
privileges.

I've re-written our logon script to get around this
problem, but apparently MS no longer provides an easy way
of reporting bugs (it used to be as simple as sending an
email to (e-mail address removed) - now they want you to
jump through hoops on the website), so I'm reporting it
via this newsgroup instead .


Brian Steele

 

[Brian Steele]

Some more information on this: apparently the bug has
something to do with the TrendMicro OfficeScan product. If
OfficeScan is unloaded, the problem no longer occurs.

Brian Steele

 

[Greg R]

Hi Everyone:

After installing SP2 on a few PCs in the office, we
discovered that several of them would suddenly crash and
reboot after certain users logged in. This did not happen
when the PCs were at SP1, and the problem appeared to be
happening only with users that did not have administrative
level access on their PCs.

After you install xp sp2 and you reboot it.
You have to enter an administrative account after you reboot with xp
sp2.

Set your polices their. Then reboot and then try limited user. I
could be wrong. I thought you might try this.


Greg R

Each account in our AD is configured to run a script after
logging on. I traced the problem down to the PCs in
question executing the following command in the logon
script:

NET USE (driveletter): /HOME /N


If that command is executed from the command prompt, the
PC bugchecks and reboots. This problem does not happen
however if the logged account has administrative
privileges.

I've re-written our logon script to get around this
problem, but apparently MS no longer provides an easy way
of reporting bugs (it used to be as simple as sending an
email to (e-mail address removed) - now they want you to
jump through hoops on the website), so I'm reporting it
via this newsgroup instead .


Brian Steele

Brian,

Here are something’s you could try. None of this may work.

Since you computer are possible networked together
Try this (sorry about the caps-pasted from cmd prompt window)

NET USE
[devicename | *] [\\computername\sharename[\volume] [password | *]]
[/USER:[domainname\]username]
[/USER:[dotted domain name\]username]
[/USER:[username@dotted domain name]
[/SMARTCARD]
[/SAVECRED]
[[/DELETE] | [/PERSISTENT:{YES | NO}]]

NET USE {devicename | *} [password | *] /HOME

NET USE [/PERSISTENT:{YES | NO}]

I would try Net use /Persistent:Yes
Before I installed xp sp2 on other computers

This is also a possibility.

After you install xp sp2 and you reboot it.
You have to enter an administrative account after you reboot with xp
sp2. Set your polices their. Then reboot and then try limited user.

Greg R

 

[Greg R]

Correted post

Brian,

Here are something’s you could try. None of this may work.

Since you computer are possible networked together
Try this (sorry about the caps-pasted from cmd prompt window)

NET USE
[devicename | *] [\\computername\sharename[\volume] [password | *]]
[/USER:[domainname\]username]
[/USER:[dotted domain name\]username]
[/USER:[username@dotted domain name]
[/SMARTCARD]
[/SAVECRED]
[[/DELETE] | [/PERSISTENT:{YES | NO}]]

NET USE {devicename | *} [password | *] /HOME

NET USE [/PERSISTENT:{YES | NO}]

I would try Net use /Persistent:Yes
Before I installed xp sp2 on other computers

This is also a possibility.

After you install xp sp2 and you reboot it.
You have to enter an administrative account after you reboot with xp
sp2. Set your polices their. Then reboot and then try limited user.

Greg R

 

[Greg R]

Just ignore my other post.

You need to give Admissive privileges to that program in limited user
mode. I know this can be done. Not sure how.

Greg R

 

[Guest]

Hi Greg:

I did try that approach on another PC. Didn't work. This
definitely seems to be a problem with SP2, TrendMicro
OfficeScan and the NET USE /HOME command being executed by
a non-privileged account.

The "solution" for me was to avoid using NET USE /HOME
altogether.


Brian Steele

-----Original Message-----

Hi Everyone:

After installing SP2 on a few PCs in the office, we
discovered that several of them would suddenly crash and
reboot after certain users logged in. This did not happen
when the PCs were at SP1, and the problem appeared to be
happening only with users that did not have administrative
level access on their PCs.

After you install xp sp2 and you reboot it.
You have to enter an administrative account after you reboot with xp
sp2.

Set your polices their. Then reboot and then try limited user. I
could be wrong. I thought you might try this.


Greg R

Each account in our AD is configured to run a script after
logging on. I traced the problem down to the PCs in
question executing the following command in the logon
script:

NET USE (driveletter): /HOME /N


If that command is executed from the command prompt, the
PC bugchecks and reboots. This problem does not happen
however if the logged account has administrative
privileges.

I've re-written our logon script to get around this
problem, but apparently MS no longer provides an easy way
of reporting bugs (it used to be as simple as sending an
email to (e-mail address removed) - now they want you to
jump through hoops on the website), so I'm reporting it
via this newsgroup instead .


Brian Steele

Brian,

Here are something's you could try. None of this may work.

Since you computer are possible networked together
Try this (sorry about the caps-pasted from cmd prompt window)

NET USE
[devicename | *] [\\computername\sharename[\volume] [password | *]]
[/USER:[domainname\]username]
[/USER:[dotted domain name\]username]
[/USER:[username@dotted domain name]
[/SMARTCARD]
[/SAVECRED]
[[/DELETE] | [/PERSISTENT:{YES | NO}]]

NET USE {devicename | *} [password | *] /HOME

NET USE [/PERSISTENT:{YES | NO}]

I would try Net use /Persistent:Yes
Before I installed xp sp2 on other computers

This is also a possibility.

After you install xp sp2 and you reboot it.
You have to enter an administrative account after you reboot with xp
sp2. Set your polices their. Then reboot and then try limited user.

Greg R

.