My Windows Server 2008 R2 Initial Configuration Steps

These are the initial steps I take to configure Windows Server 2008 R2:

  1. Disable server manager refresh
  2. Disable server manager at startup
  3. Set timezone
  4. Configure working (static IP, disable IPv6)
  5. Set computer name
  6. Enable automatic updates (and download them)
  7. Enable remote desktop
  8. Disable initial configurations window at startup
  9. Restart
These will be some of the steps I will automate using Windows Deployment Services.

Popular posts from this blog

Get local computer UUID/GUID using Windows Powershell

Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct  | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
Read more

PSLoggedOn Getting Started on Windows Server 2008 R2

Image
PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se
Read more

Citrix Printing Series - Auto-Creating Session Printers

Image
In addition to or as an alternative to creating client printers, XenApp and XenDesktop allow an Administrator to specify which network printers should be created within each session. This process is controlled using the "Session Printers" policy. See the user policy below: You can very cleverly configure what's known as Proximity Printing, which involves the use of the "Session Printers" policy, the "Default Printers" policy and a filter based on a geographic indicator such as an IP Address or client name. Use Session Printers and or Proximity Printing when you have one of the following scenarios: Thin Clients are used that cannot connect to network printers Laptop users roam throughout sites
Read more