window server 2008 R2
Hi all,
Hi,i am a newbie to windows server,Currently i am helping my boss to set up a server in the office. And i have tons of question for the windows server.And i believe some of the question may be seem quite stupid to you all,but i am really willing to get know
about that,and i am wish to get an answer from your all.
Here is my situation:
i have a server which come with windows server 2008 r2 enterprise 64bit.and it need to get connect with 5 workstations.Which all the workstations is running a windows 7 professional.I am able to create a Domain in the server and currently all the workstation
is able to connect to the domain finely.
But now i do face up this few problem:
1.May i know that all the software install to the server,can it be use by the workstation once they join the domain?And how the procedure to do so?
2.I am aware that all clients are able to keep their data in the server,and i need to know how to do so.
3. Now for all my workstation is using the same password to log in to the domain,can i set different User password to different User? and could i able to lock the local user machine? cause my boss just wanna let them to log in to domain once they on the
PC.
4. I do have a network print server.Do i need to do any more configuration on it?
This is some of the difficult problem for me,i do have more for the server,but currently i do need to solve this problem first.I wish to get an answer from your all,even is just some clue of it for how to do so.And i am really sorry if i still miss out of
any important info.just let me know if really miss it.
And thousand thanks for all your guys...i know i am totally weak on server.So hopefully yours guys could lent a hand.
Thanks.
July 17th, 2010 7:16am
1. software installed on the server isnt automatically usable by the workstations. while there are applications that can be used remote (webapplications would be an example, hosted on the server once, used by all workstations), say installing office on the
server wont make it usable on the workstation as such, youd still need an office installation on each workstation
2. in server manager you can add the role file server, there a wizard then that helps you set up a share, which the workstations can access
3. in server manager, theres domain users and computers. there you can create users. they should have different passwords.
4. if its eg an hardware print server, no, nothing should change there. (if you use the print server role of your domain controller you can decide if you make the printer browsable in your network and who is allwed to print on it)
Free Windows Admin Tool Kit Click here and download it now
July 17th, 2010 12:48pm
Hello,
as you are not familiar with a domain administration i hihgly suggest that you take a course on it. Administration is not that easy as installing it. You need basic knowledge about Active Directory, DNS, Group policies(GPOs), Active Directory aware backup,
configuring permissions and some more.
1. software installed on the server is not available for users, except web based applications are installed. Server applications are built for specific roles.
2. to have data from the users on the server you need shared folders, configured with needed permissions on the share level and NTFS permission on the folder itself.
3. User management in a domain is done from Active directory users and computers management console. Here you find a basic overview for starting where you should built your own Organizational Unit(OU) topology for the company. OUs enable you to apply GPOs
for the computers and users for your needs
4. you have to install the printer within the network with it's own ip address and configure it on the server as network printer and share it in Active directory, then users can add it with the printer wizard.
As said before, administration of a domain involves a lot of different needs. Also it is recommended to have a t least 2 DC/DNS/GC per domain and use a domain member server for additional services like file/print server A domain controller should only do
it's basic tasks and shouldn't be used for applications like Exchange for example.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
July 18th, 2010 1:17pm
Thanks Bros,thanks for the info given,thousand thanks to your guys. i have already request a course from the boss on this.By the way, really appreciate yours guys for the info and clues.However i may not get throught this,but at least i have some clues of
it.Really thanks about it.
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2010 5:24am