HI Server Expert,

I am trying published a shared drive on my server 2008 R2 AD. however, after I am adding the shared drive on the active directory user and computers, I am also need to see the shared drive when I trying to browse for the shared drive.

please advise.

Thanks.

But have you share this folder physically on any servers First? Publishing Share Folder in active directory is not creating physically shares. You have to first creating any shared folder and next publishing it

Hi There,

Yes. I  have created a shared folder and give full permission to everyone. so if I can use \\ to see the shared drive and access it, how should I publish it at AD so I can see it in my network?

Thanks

To find this published folder in AD you have to use tools to searching AD like ADUC. If station or server ( i see this option on my windows 2012 member server )  is in domain and you open Network on top bar you find "Search Active Directory" button. Run this and set find category on to "Shared Folders" in "Entire Directory"
This find you all published folders in AD

Sorry for my English.

To find this published folder in AD you have to use tools to searching AD like ADUC. If station or server ( i see this option on my windows 2012 member server )  is in domain and you open Network on top bar you find "Search Active Directory" button. Run this and set find category on to "Shared Folders" in "Entire Directory"
This find you all published folders in AD

Sorry for my English.

Hi Jakub,

I think you misunderstand with what I need here. Basically, I am creating shared folder in the AD by using Active Directory Users and Computers. After we create shared folder there, it should be seen under network even from any clients computer right?

Thanks.

I think I understand what's going on. You want the shared folder after publishing in AD will automatically appear on all the stations in the "NETWORK" windows, right?
It will not. In "NETWORK" Window you find only servers and computer which are nearly your station but not shared folders. Publish in AD is used to easily find such a resource in the network but by searching in the AD use for example ADUC. I think better idea will be use DFS.

Hi Jakub,

Yes. this is wat I want. We want to be actually to have one folder which can be seen by two servers, one in premise and the other one on the cloud for the SQL server replication to be happen. Since the sql server is not able to use normal mapped drive, the only way is to publish the shared folder in AD so it can be seen. But no matter I did, the shared folder is not there.

Another thing is even I clicked on my computer and go to network, I can only see some of the computers or servers but not all in premise. what is happening here? since we are belongin to the same network, we should see the list of all computers/servers in the network right? some more the list will be different from computer to computer.

I don't know what is DFS and how to do that btw.

please advise.

i don't understand clearly your concept described in first part of your response. Could you give me more information to understand it and could help you? you have two servers with one shared folder on each of them. One server on-site and one out-site network , right? and you have SQL server which you want copy data to this shares?
Second parts of your response is depend of which type of OS is use, if computers enable firewall or enable network discovery, if on network adapter is enable "File and Printer Sharing for Microsoft Networks", etc.

DFS --> https://en.wikipedia.org/wiki/Distributed_File_System_(Microsoft)

i don't understand clearly your concept described in first part of your response. Could you give me more information to understand it and could help you? you have two servers with one shared folder on each of them. One server on-site and one out-site network , right? and you have SQL server which you want copy data to this shares?
Second parts of your response is depend of which type of OS is use, if computers enable firewall or enable network discovery, if on network adapter is enable "File and Printer Sharing for Microsoft Networks", etc.

DFS --> https://en.wikipedia.org/wiki/Distributed_File_System_(Microsoft)

Hi Jakub,

By using the DFS seem to be more complicated for me.

Actually, What is need is to create a shared folder that could be recognized by both database server in the premise and also on the cloud. I know that creating a shared drive and then mapped to both of the server is very easy, but SQL server is not recognizing the mapped drive. So, I plan that if I could publish the shared drive on the AD, then it should be easier.

The concept of SQL server replication is in this way. The In premise SQL Server will always copy the log files to the folder inside the shared folder and then the cloud SQL Server will establish connection to the shared drive and copy the log files from the shared drive and apply it to the cloud database.

The Database Administrator has the difficulty of mapping the mapped shared drive in the sql server as sql server is not recognizing the mapped shared drive. if the shared folder in the active directory, there might be high chances that the sql server able to detect it.

Thanks.

Regards,

Hi,

If you go to Network, click on Search Active Directory in Network tab, change to "Shared Folders" in "Find:", it will help list the folders you published in ADUC.

My question is that why not directly use the UNC path of the shared folder but have to use a published path?

Hi,

If you go to Network, click on Search Active Directory in Network tab, change to "Shared Folders" in "Find:", it will help list the folders you published in ADUC.

My question is that why not directly use the UNC path of the shared folder but have to use a published