Mark Minasi's Tech Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 39
Reply with quote  #1 
Windows Server 2016 Standard server.  I first created a share named UserFiles$ and set all the appropriate permissions and NTFS settings according to a publication for creating user home folders.  I set the profile in ADUC to \\server\sharename$\%username% with an appropriate drive letter assignment.  All of the folders were created as expected with the share & NTFS permissions but the share is not accessible from the client as the article stated it would be.... "System cannot find the drive specified" error.  Before I create a group policy setting to set the drive with the clients, is it required to create a GPO to apply to the clients before the drive will be accessible?
0
donoli

Senior Member
Registered:
Posts: 530
Reply with quote  #2 
I googled the error message in quotes exactly as you posted it. There were tons of hits but they were related to other scenarios. One of the hits was on the Symantec site which points to AV. Another hit pointed to a firewall setting.
0
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 39
Reply with quote  #3 
Don,
I thought about the AV installed but it turns out I was just a bit impatient.  It took somewhere around an hour or two and the share showed up.  It could be accessed via command line prompt but it doesn't show up in Windows Explorer.  Fix for that was a GPO shortcut and all is good.  Thanks for taking the time to look into it though.
0
donoli

Senior Member
Registered:
Posts: 530
Reply with quote  #4 
I'm glad that all is well. When you accessed by command line, was the command prompt running as administrator?  It's strange that something would block it one way but not the other.
0
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 39
Reply with quote  #5 
Quote:
'm glad that all is well. When you accessed by command line, was the command prompt running as administrator?  It's strange that something would block it one way but not the other.


It didn't matter as I issued a "net use" to view any shares and it didn't show up right away.  Did not matter whether the command prompt was issued as administrator or user.  I took it from everything I read that it would show up right away.  From what I can see, if the home folder share is created while clients are logged in, the accessability to the share is governed by a timer whose setting is established somewhere within the server or AD settings.  I do know that if the client reboots and logs back in, the home share becomes available right away.  I just wasn't patient enough, one of those things where you think it should happen right away but didn't.  Here in Hawaii I label those kind of unexplainable occurences as a "minnie hoonie" [cool]
0
donoli

Senior Member
Registered:
Posts: 530
Reply with quote  #6 
The 2 most important thing is that it works & you're in a warm state not necessarily in that order.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.