Windows Issues
From Stadm
Jump to navigationJump to search
Contents
Purpose
- Document issues I've run into with Windows and what I have done to fix/remedy the situation
AD
Profiles
- So Windows doesn't like to be compatible with roaming profiles across different versions of windows
- even better it doesn't automatically creating different profile extensions so supporting multiple versions of windows becomes a mess in a domain environment with roaming profiles
- Incompatibility list:
Profiles are compatible only between the following client and server operating system pairs: Windows 8.1 and Windows Server 2012 R2 Windows 8 and Windows Server 2012 Windows 7 and Windows Server 2008 R2 Windows Vista and Windows Server 2008
- Links:
- Fix is quite easy, just add a dword to the registry, we'll just make a gpo out of it
- Open regedit(Or make this a GPO) and navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\ProfSvc\Parameters
- add a DWORD named UseProfilePathExtensionVersion and set the value to 1
- Different profile version extensions
Windows 8.1 and Windows Server 2012 R2(.V4) Windows 8 and Windows Server 2012 (.V3) Windows 7 and Windows Server 2008 R2 (.V2) Windows Vista and Windows Server 2008 (?)
Network
IPV6
- Ipv6 takes priority for local address lookups
- can view with
netsh interface ipv6 show prefixpolicies