|
Sorry was rambling on a bit there (and probably here too!)…
As an example, you mention problems getting policies down to XP.
Yep, this is all to do with the fact that XP doesn’t bother to wait for network connections before allowing people to log on. This can result in policies, roaming profiles, logon scripts and drive mappings not being run/mapped as the network connections they reside on are not available.
There is a policy setting that forces XP to wait for network connections, but I’ve found that this does not solve the problem in all cases – particularly with older Cisco switches which are slow to negotiate. As a result I had to apply another policy to force a logoff if a roaming profile fails to load, although this does not look good from a users point of view!
And so on and so on… this is just a clipit of the kind of grief you’re likely to come across.
|