<div>
Not sure how the database is configured but it may also be possible to create a hidden share on that server by putting the $ at the end of the shared folder name. This would hide the folder from displaying if you browse to the server. Only users that know the full path would be able to access the data. <br />
<br />
You could also look into restricting the read access to the database to only those users who are supposed to view it.
</div>


Not sure how the database is configured but it may also be possible to create a hidden share on that server by putting the $ at the end of the shared folder name. This would hide the folder from displaying if you browse to the server. Only users that know the full path would be able to access the data.

You could also look into restricting the read access to the database to only those users who are supposed to view it.

<div>
You can do as xxdcmast stated with the hidden share, but also as he said, it is not the most secure as people who may know the full path can still access it. Why not set permissions on the folder and create a GPO or share permissions for only those that are supposed t have access.
</div>


You can do as xxdcmast stated with the hidden share, but also as he said, it is not the most secure as people who may know the full path can still access it. Why not set permissions on the folder and create a GPO or share permissions for only those that are supposed t have access.

<div>
<div class="content wysiwyg-content">
Have a server which is not the domain contoller , that runs a database only , customer wants only the users who use the database to be able to see the server ,problem I see is most of the workstations are Vista Business 
</div>
</div>


Have a server which is not the domain contoller , that runs a database only , customer wants only the users who use the database to be able to see the server ,problem I see is most of the workstations are Vista Business 

hiding fileserver from some people on the domain

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.