Prevent downloading of roaming profile

[jaeddy]

My department has a primary site using win2k pro machines on an NT 4.0 doamin, and a fail over site which uses NT4.0 Workstation machines on the same NT 4.0 domain. Roaming profiles are in use at the primary site.

Two problems have arisen:

First, there are issues when folks go to the failover site and log in- the profiles get hosed up.

Second, due to the relatively slow wan link to the fail-over site downloading the profiles can take several minutes- a nuisance we would prefer to avoid.

The fail-over site has its own BDC. The profiles are located on the PDC at the primary site.

I've tried putting system policies in place on the machines at the failover site to default to using a local profile, but they still download the roaming profile from the PDC.

Any ideas? I'm poking through the registry now to see what I can come up with but any advice would be welcome.

 

[wolluf]

Policies? (How many machines at fail over site?) Could set up a policy for each machine to use local profiles.

 

[jaeddy]

There are three workstations and a BDC. I did set up policies to default to local on those machines, but it blithely ignores this and uses the roaming profile instead.