A clients office has recently started to upgrade to Windows 10 from Windows 7
They've been running a couple of machines with 10 to check all works OK with their software. The machines which were upgraded started to develop a strange fault; Windows would report that the connection to the mapped drives had dropped
At face value it looked like the problem was that the network had a fault, potentially a failing switch, NIC or cable but the problem persisted after changing ports and switches.
Fast forward through more investigation and the problem was eventually tracked down to how the mapped drive was being made using Group Policy
For some reason, if the drive is mapped using the CREATE option then Windows 10 appears to drop the mapped drive connection (for only a brief moment) to re-create it again. The Windows 7 PCs don't seem to mind this and it doesn't cause any problems
The resolution was simply to change the mapping from CREATE to UPDATE and the problem was solved
They've been running a couple of machines with 10 to check all works OK with their software. The machines which were upgraded started to develop a strange fault; Windows would report that the connection to the mapped drives had dropped
At face value it looked like the problem was that the network had a fault, potentially a failing switch, NIC or cable but the problem persisted after changing ports and switches.
Fast forward through more investigation and the problem was eventually tracked down to how the mapped drive was being made using Group Policy
For some reason, if the drive is mapped using the CREATE option then Windows 10 appears to drop the mapped drive connection (for only a brief moment) to re-create it again. The Windows 7 PCs don't seem to mind this and it doesn't cause any problems
The resolution was simply to change the mapping from CREATE to UPDATE and the problem was solved
No comments:
Post a Comment