If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more
I have customer, which is doing in-place upgrades from Win10 to Win11. It's out of discussion, that this approach is not the best.
He did many of upgrades ( 10 + at least ) and only on one workstation he got troubles. NSS drives can be mapped, but are super slow when opening folders and/or opening Office document. Problem aren't limited to OES client, worse situation is with Samba drives, which can't be mapped.
Anyone faced this situation ?
Thanks for hints.
David
Hi,
looks like a problem with the redirector, maybe uninstalling the OES client first and then try to fix the smb problems whether they still exist.
Also, you can check the registry, we always use the PermanentGoodNameCache for the OES servers with ncp connections.
https://support.microfocus.com/kb/doc.php?id=7015227
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Client\Parameters]
"GoodNameCacheList"= name of the oes servers
"PermanentGoodNameCacheEnabled"=dword:1
The problem is that with this inplace update method, you inherit all the problems the workstation might have collected over the (many) years of operation. Something we know that windows doesnt like.. 
Always try do do a clean/fresh rollout/deployment, whenever its possible.
Hi,
looks like a problem with the redirector, maybe uninstalling the OES client first and then try to fix the smb problems whether they still exist.
Also, you can check the registry, we always use the PermanentGoodNameCache for the OES servers with ncp connections.
https://support.microfocus.com/kb/doc.php?id=7015227
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Client\Parameters]
"GoodNameCacheList"= name of the oes servers
"PermanentGoodNameCacheEnabled"=dword:1
The problem is that with this inplace update method, you inherit all the problems the workstation might have collected over the (many) years of operation. Something we know that windows doesnt like..
Always try do do a clean/fresh rollout/deployment, whenever its possible.
David
Support
Documentation
Learning Services
Partner Programs