HI Hersheys99,
This is a bit of a random thought but....
Have you tested with this GPO setting.
- Always wait for the network at computer startup and logon (Computer->Administrative Templates->System->Logon)
Regards,
Geoff
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
we have an existing on prem environment,
this is synced to azure with the v2 connector,
the connector syncs specific user OU and workstation OU
our servers OU is not currently synced.
we have successfully hybrid joined our workstations and they show MDM as intune and dsregcmd shows them azure joined and domain joined.
we have on prem file shares that are pushed VIA gpo, they are set as create and reconnect.
when users sign into their workstations, using domain username and password (not windows hello)
they see the file shares but attempts to browse give them a "location cannot be found" error.
once we do a gpupdate /force, the drives become available.
upon log out and log back in, same behaviour "location cannot be found" rinse and repeat.
this happens on windows 10 and 11 devices both.
we have checked for DNS entry errors, we have checked for conflicting intune policies / GPO errors, we found some duplicated workstation entries in Azure where they show not MDM connected, so we removed those leaving only the registered / hybrid joined device ID.
so my questions now are.
does our FS need to be hybrid joined? (we prefer not to as its offline)
does the OU in our onprem AD at least need to be synced so Azure knows where to point the workstations?
is there something I'm missing to the setup? firewall entries that need to be whitelisted perhaps?
HI Hersheys99,
This is a bit of a random thought but....
Have you tested with this GPO setting.
Regards,
Geoff
@hersheys99, Thanks for posting in Q&A. It sounds like you're experiencing a complex issue with your hybrid environment and file shares. Here are my answers for your question:
gpupdate /force
resolves the issue temporarily suggests that there might be a delay or issue in the policy application.If there's anything unclear, feel free to let us know.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.