remote desktop

[Reed Wiedower]

When I attempt to have users use XP Remote Desktop to connect to their local
machines on our domain, they're often presented with an Office error saying
that "a major hardware change has occurred" and then forcing them to attempt
to re-register remotely. Since the users in question have office both on the
machine they are connecting with as well as the machine they're connecting
to, is there any way for me to prevent this? Obviously, failure to register
results in reduced functionality mode which isn't acceptable...

end of line,

Reed Wiedower

 

[Lanwench [MVP - Exchange]]

When I attempt to have users use XP Remote Desktop to connect to
their local machines on our domain, they're often presented with an
Office error saying that "a major hardware change has occurred" and
then forcing them to attempt to re-register remotely. Since the users
in question have office both on the machine they are connecting with
as well as the machine they're connecting to, is there any way for me
to prevent this? Obviously, failure to register results in reduced
functionality mode which isn't acceptable...

end of line,

Reed Wiedower

Are you sure it's 'register', and not 'activate' ? Registration of MS
products is not mandory. If you can get the exact text of the error message,
you might wanna post in a TS or XP / remote_web group for best results. I'm
presuming you do not see this problem with the same user logging in at the
console, right?

 

[Ada Pan [MSFT]]

Hi Reed,

According to your description, my understanding on this issue is: When the
users use XP Remote Desktop to connect other machines, they are often
prompted with an Office message "a major hardware change has occurred" if
launching Office applications.
If I misunderstood your concern, please feel free to let me know.

First of all, I would suggest you check if this issue occurs when you log
on the computer locally instead of remotely.

Based on my and experience and research, this message is normal if any
hardware or driver is changed on the computer which connecting to. It is
totally no related with the configuration on the computer which connecting
with.

Please check if the users change any driver or hardware on the computers
which connecting to. If so, Office will consider it as another machine and
require to be activated. You may have to reregister to reactivate Office.

If there is anything unclear in my response or you need further assistance
on this issue, please feel free to let me know.

Regards,

Ada Pan

Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Reed Wiedower]

1.) You are correct in summarizing the issue.

2.) The issue never occurs locally. It only occurs when users connect using
XP Remote Desktop.

3.) No hardware changes are being made to the machines. If a user logs on
locally, they are fine. If they then walk a few feet away, log into another
machine, and connect to the original machine using XPRD, the error crops up
again.

4.) If the original user *leaves himself logged into his machine* and then
connects with XPRD, the problem does not occur as long as the office
application is not restarted.

5.) Even if the user wished to reactivate office, they are unable to,
because the dialog box does not allow interaction with the cd-rom drive. It
merely looks in one location and, not finding the particular msi file it
wishes to, coughs up an error.

So, in short, no hardware changes are occurring. Thus, the message has to be
related to the fact users are connecting using XPRD.

end of line,

Reed Wiedower

 

[Reed Wiedower]

Sorry...re-activate is what I meant to say.

The XP forums directed me to this forum because they claimed the problem had
to do with Office, not with XP Remote Desktop.

end of line,

Reed Wiedower


"Lanwench [MVP - Exchange]"

 

[Bob Buckland ?:-\)]

Hi Reed,

Does the titlebar of the dialog say it's
an Office rather than a Windows activation?

=======
Sorry...re-activate is what I meant to say.

The XP forums directed me to this forum because they claimed the problem had
to do with Office, not with XP Remote Desktop.

end of line,

Reed Wiedower >>

 

[Ada Pan [MSFT]]

Hi Reed,

Thanks for your update.

Based on your description, I would suggest you collect more inforamtion for
further troubleshooting:

1. Check whether these problematic users are configured to use roaming
profiles.

2. Create a new local account and logon the system locally without using
RDP. Check whether it works.

3. Please also check he has configured Terminal Services User Profiles for
the domain users.

I look forward to your process.

Regards,

Ada Pan

Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Reed Wiedower]

1. Yes, all the users in the domain use roaming profiles.

2. Yes, it works.

3. No users are setup to use terminal services user profiles.

I am unclear as to why any of these steps would result in a "major hardware
changes" error on the client side. What should I try next?

end of line,

Reed

 

[Reed Wiedower]

Yes, it's an Office Activiation error dialog. The rest of the OS, as well as
programs, work fine. Only Office switches into Reduced Functionality Mode
after the activation wizard fails.

end of line,

Reed Wiedower

 

[Ada Pan [MSFT]]

Hi Reed,

Thanks for your update. I am sorry for the delay due to the weekend.

As I know, there is no difference to use Office if you log locally or
remotely on a computer. By default, Office System is installed in Local
Machine and can be used by any users log on this computer. Based on your
description on this problem, it is really particular issue. We may need
much information to troubleshoot this problem.

I would like to confirm you the following questions:

1. Do all or some specific user accounts in the domain experience the
problem?

2. Do all or some specific computers in the domain experience this problem?

3. What version of Office is installed on the computers in the domain?

In the meantime, I would suggest you perform the following steps to collect
more information for further troubleshooting:

Step 1: Getting the domain information
---------------------------------------------------
1> On the destination computer, click Start - Run, type "cmd", then click
OK.
2> Type "gpreult /v >c:gp.txt" and then press Enter. (Without quotation
marks)
3> Wait for a minute, and then send the gp.txt file under C:\ to me.

My e-mail address is: < (e-mail address removed) >.

Step 2:
----------

1> Log all the users off on the destination computer.
2> RDP to the destination computer by logging as any user account
experiencing this problem.
3> Check the subfolders' name under C:\Documents and Settings.
4> Tell us the user account you log on and the detailed list under the
C:\Documents and Settings folder.

For example:
User account: AdaPan
The list of Subfolders:
Administrator
All users
Default Users
LocalService
NetworkService
adapan

Step 3:
----------
1> On the destination XP computer, use Registry Editor to add the following
registry value (or modify it, if the value already exists):
Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon
Value: UserEnvDebugLevel
Value Type: REG_DWORD
Value Data: 10002 (Hexadecimal)

2> Restart the destination computer.
3> RDP to the destination computer to repro the issue.

Please send me the C:\windows\Debug\UserMode\Userenv.log file.

Step 4
----------
1. Go to DC, open Active Directory Uses and Computers. Right click the
Domain Node, select New ->Organization Unit to create a new OU.
2. Move the two test machine account from the Computers container to this
OU, and then move the two test account from USERS container into this OU.
(If you have moved the Computer Account or User account to another
location, please move them from there.)
3. Right click the OU, select properties, go to Group Policy tab, click New
button to create a new OU. Then click Edit.
4. Navigate to Computer Configuration\Administrative Templates\System\User
Profiles, Enable the policy: Delete cached copy of Roaming Profile.
5. On the two XP client computers, go to command prompt, type following
command: GPUPDATE /target:computer /force.
6. Restart the XP client computer, logon by the domain user account, then
log off, logon by local administrator account to see if the local cached
domain profile is deleted.
7. After the local cached domain profile is deleted, logon from another
computer by RDP to see how everything is going.


Step 5
----------
If the issue still exists under this situation, besides providing me with
the latest userenv.log file, please download the network edition of
MPS_Report. Email me with the cab file.
Network MPS Report
-----------------------------
a. Visit
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_NETWORK.EXE to download the file.

b. Run the MPSRPT_NETWORK.EXE

c. Wait for 10~15 minutes.

d. Open Windows explorer, navigate to
%SYSTEMROOT%\MPSReports\Network\Reports\cab\

e. Send the .cab file directly to me.


Step 6
---------
On the destination computer:

1> Click Start, click Run, and then in the Open box, type "MSCONFIG"
(without the quotation marks). Click OK.

2> In the System Configuration Utility (MSConfig) window, click to select
the Selective Startup button.

3> Click to clear the check mark from the "Load startup items" below
Selective Startup.

4> Click the Services tab, click to check the "Hide All Microsoft Services"
box, and remove all the check marks from the remained Non-Microsoft
Services. *note that please make sure that you do not uncheck the Microsoft
services.

5> Click OK to close the MSConfig window. Click Yes when you are asked to
restart your computer in order to enable the changes.

6> After restarting, logon from another computer by RDP to see how
everything is going.


Step 7
---------
Please take the screenshot of the re-activation dialog box when this
problem occurs and send it to me.

I hope the information will help us narrow down this problem.

Please update me with the needed information at your earliest convenience.

Regards,

Ada Pan

Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.