Roaming Profiles

  • Thread starter Thread starter Alec Gagne
  • Start date Start date
A

Alec Gagne

Hello All,

I have a customer experiencing a problem running an application created in
VFP8. They use Roaming Profiles. A user can login to a Win2000 machine on
the network and run the APP no problem. However, once that same user logs
into the network on an XP machine they can no longer run the application on
any of the W2000 machines. Seems that XP is changing the Roaming Profile on
the server in such a way as to screw up W2000's ability to run the same APP.

Does anyone have any experience with this issue and/or know how to fix it?

Here is an email from my customer which helps explain it:
*********************************************************
Regarding the Windows 2000/XP Roaming Profiles Problem:

Removing the file NTUSER.DAT in the individuals profile directory on the
server and from their profile directory on the Windows 2000 Workstation,
VFP8 (and Crimestar) will function again. Removing this file forces the
workstation to load the Default user registry entries on login, rather than
the stored settings.

Since this works, I have to conclude that a registry setting in HKEY_USERS
is getting changed by Windows XP and causing problems for Windows 2000. I
can't find it. If you can find out what registry settings are used by VFP,
I should be able to come up with a workaround.

*********************************************************

TIA

Alec
 
Hi,

As far as I know, this is something Microsoft overlooked; you get
similar problems in a mixed NT/2000 environment.

Solutions:

1. Don't upgrade to XP - this is the coolest, and it saves a lot of
money, and your users can still get their work done instead of watching
skateboarding vids all day.

2. Make sure you only run ONE Microsoft O/S enterprise-wide. So much for
interop:(

3. Seek out the exact reg keys that are causing the problem and fix them.
 
Hi Gerry,

Thanks for the reply. I agree, I don't think it is wise
to mix OS' and from all I have heard Roaming profiles are
a pain in the #**. Having said that, I don't control the
network or IT decisions at this client site.

Any ideas on how to:

"Seek out the exact reg keys that are causing the problem and fix them."?
 
Alec said:
Thanks for the reply. I agree, I don't think it is wise
to mix OS' and from all I have heard Roaming profiles are
a pain in the #**. Having said that, I don't control the
network or IT decisions at this client site.
Click to expand...

In general roaming profiles are the "correct" way to do it. Not having
them is even worse, especially when it comes to putting a new machine on
someone's desk or when someone logs into a different machine and wants
to check their e-mail. It's also better for disaster recovery.
Any ideas on how to:
Click to expand...

You'll have to explain your role? You appear to be saying you're not the
IT department at the clients site, are you therefore the app vendor? If
so, then you'll have to disect your app and work out what HKCU keys it's
trying to use, compare these with logged on users at the site (regedit)
and then decide what to do.
 
Hi Gerry,

Thanks!

--

Alec


Gerry Hickman said:
In general roaming profiles are the "correct" way to do it. Not having
them is even worse, especially when it comes to putting a new machine on
someone's desk or when someone logs into a different machine and wants
to check their e-mail. It's also better for disaster recovery.


You'll have to explain your role? You appear to be saying you're not the
IT department at the clients site, are you therefore the app vendor? If
so, then you'll have to disect your app and work out what HKCU keys it's
trying to use, compare these with logged on users at the site (regedit)
and then decide what to do.
Click to expand...
 
Back
Top