A user is seeking suggestions for a custom script action to identify the root cause of drive mapping issues for a customer. More information is needed on what the script should achieve. The customer deploys network drives via GPO, and the issue could be due to reasons such as VPN or insufficient permissions. The user wants to gather as much information as possible when a drive is not mapped, as a gpupdate/force does not provide insight into the cause of the issue.
Read the entire ‘Addressing Drive Mapping Issues with a Custom Script Action’ thread below:
i have customer who needs to analyze drive mapping issues / idelly to identify the root cause. any suggestions for a custom script actions?
can you perhaps share a bit more details ?
what is that you want to see ?
I have a script i our environment that shows the drives that are mapped (network mapped drives )
Customer is deploying Network Drives via GPO and it happens quite often and sporadicly that some are not mapped. Sometimes its the VPN, sometimes its insufficent permissions …etc etc. The Idea would be to get so much Info as possible when a drive is not mapped.
A gpupdate /force can fix it but then we dont know why it happend.
Continue reading and comment on the thread ‘Addressing Drive Mapping Issues with a Custom Script Action’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops, ControlUp Scripts & Triggers