Windows Server 2.Server Core Part 6 Configuration 4sysops.Ive discussed the built in tools available to you in Server Core in the previous article in this series.Today, lets put them to good use to turn a fresh Server Core installation into a proud member of our networking environment.Microsoft Windows Server 2012 Setup Keyboard InputPerhaps even a founding memberServer Core Default settings A fresh Server Core installation of Windows Server 2.Its hostname is a random name, beginning with WIN followed by 1.Net. BIOS name. It is a member of the WORKGROUP workgroup.Its network interface cards are set to request an IPv.IP address from a DHCP server.If it does not receive an IP address from a server, it will configure a 1.Automatic Private IP Address with 1.RFC 3. 92. 7. IPv.Remote Management through both WINRS and WINRM is enabled by default for the local network.Remote Desktop is disabled by default.Microsoft Windows Server 2012 Setup Keyboard To Ipad' title='Microsoft Windows Server 2012 Setup Keyboard To Ipad' />Windows Update is set to manual by default.Its default time zone is UTC 8 0.Pacific Time U. S.Canada and is set to synchronize with time.By default, you will be notified when the clock changes.The Customer Experience Improvement Program CEIP is not joined.Depending on the installation media used, the Server Core installation is either configured with a Generic Volume License Key GVLK and configured to automatically activate against a KMS Server, or is configured through Active Directory based Activation.If you have entered a product key during Windows Setup, the Server Core installation will be configured to activate depending on the type of product key.Now, these settings might not be to everybodys pleasing, so lets find out how to change them Changing the IPv.To change the IPv.Describes the update for Windows RT 8.Windows 8. 1, and Windows Server 2012 R2 that was released in April 2014.Windows Deployment Services Getting Started Guide for Windows Server 2012.Despite having begun jointly developing a new operating system, OS2, with IBM in August 1985, Microsoft released Microsoft Windows, a graphical extension for MSDOS.Server Core installation, type sconfig.Select the network adapter from the list by typing its index number.Type 1 and then S to provide a static IPv.Type the IP address to use, and then press Enter.Then, type the Subnet Mask and press Enter.Or just hit Enter when the default Subnet Mask is what you want.Then, type the IP address of the Default Gateway nearest router and press Enter.Tip If you want to undo your action and revert the server back to being a DHCP client, simply go into Network Settings option 8 in sconfig.D. Your Server Core installation will not be able to go onto the Internet, or reach Active Directory, since it doesnt yet have the proper name resolution.The most convenient way to do that is by specifying one or more DNS servers.While in Network Settings with the network adapter selected, type 2.Then, type the IP address of your preferred DNS server and press Enter.Tip To remove your DNS server configuration, while in Network Settings with the network adapter selected, type 3.To script an IPv.The following two commands will change the IPv.DNS server to resolve names.However, because the netsh.Power. Shell is more appropriate.Use the following one liner to change the IPv.Server Core installation.New Net. IPAddress Interface.Index 1. 2 IPAddress 1.Prefix. Length 2.New Net. IPAddress Interface.Index. 12 IPAddress.Prefix. Length. 24.Set Dns. Client. Server.Address Interface.Index 1. 2 Server.Addresses 1. 92. Set Dns.Client. Server. Address Interface.Index. 12 Server.Addresses1. 92. Simply change the italic values to values that make sense for your environment.Changing the hostname To change the Net.BIOS hostname of your Server Coreinstallation, type sconfig.Select option 2. Type the new hostname and press Enter.In the pop up titled Restart, answer Yes to the question You must restart your computer to apply these changes.Restart now. If you want to script changing the hostname, you can use netdom.The following command can be used.Netdom renamecomputer localhost newname New.Computer. Name force reboot 1.Netdom renamecomputer localhostnewname New.Computer. Nameforcereboot.In Power. Shell start it up by typing it at the command line, use the following two commands.Rename Computer New.Computer. Name. 1Rename Computer New.Computer. Name. Restart Computer Joining a domain If you want to make your Server Coreinstallation a member of your Active Directory environment, again, type sconfig.Press D and then type the DNS name of the Active Directory domain to join, and press Enter.Then, provide the user name for an account with sufficient rights to join the computer to the domain, and press Enter.A separate prompt will pop up, asking for the password.Alternatively, you can use the following command.Netdom join localhost domain domain.Netdom join localhostdomain domain.Or, fire up Power.Shell by typing it at the command line and use.Add Computer Domain.Name domain. tld.Add Computer Domain.Name domain. tld.Server Core Domain Join.After successfully joining the Server Core installation to the domain, use Restart Computer to restart the server.Enabling Remote Desktop To enable a Remote Desktop session on your Server Core installation, you can use sconfig.Option 7 offers the ability to enable it by typing E and pressing Enter or disable it by typing D and pressing Enter.When you enable it, you can enable it with or without Network Level Authentication NLA.Enabling it will be more secure, but you wont be able to make a connection from Windows XP Service Pack 2 and earlier versions of Windows.If you want to do this the manual way, using SCReg.Edit. wsf is the easiest way.The following command enables Remote Desktop.Cscript C WindowsSystem.SCReg. Edit. wsf AR 0.Cscript. C WindowsSystem.SCReg. Edit. wsfAR0.This command will also automatically create the firewall exception for you.This makes using SCreg.Edit. wsf the preferred method over the various registry methods.Note, however, that this command is case sensitive.Configuring Windows Update Although it would be a best practice to configure Windows Update centrally with Group Policy and one or more Windows Server Update Servers, you can also enable it manually.Configuring it through sconfig.Option 5 offers you the choice between Automatic and Manual.Automatic settings will check for and install updates every day at 3 0.AM. Option 6 lets you download and install updates.One of the choices here is to search for All updates or Recommended updates only.If you want more granular control over Windows Update settings, SCReg.Edit. wsf comes to the rescue once again.The following command enables automatic Windows updates.Cscript C WindowsSystem.SCReg. Edit. wsf AU 4.Net stop wuauserv.Net start wuauserv.Cscript. C WindowsSystem.SCReg. Edit. wsfAU4.Net stop wuauserv.Net start wuauserv.If you want to change the time Windows updates are installed automatically, you can change the value of the Scheduled.Install. Time key in HKLMSoftwareMicrosoftWindowsCurrent.VersionWindows. UpdateAuto Update.Use Regedit. exe for this.If you want to check which Windows updates have been installed, run the following command Wmic qfe list.Changing the screen resolution In previous versions of Windows Server, it was a bit tricky to change the screen resolution.Most of the time, Server Core admins resorted to third party tools.In Windows Server 2.Microsoft introduces two new Power.Shell cmdlets. Get Display.Resolution. Set Display.Resolution. Get Display.Resolution. Set Display.Resolution. The Set Display.Resolution cmdlet is really useful.Start Power. Shell by typing it at the command line.Then, the following command will change the display resolution to 1.Set Display. Resolution Width 1.Height 7. 68 Force.Set Display. Resolution Width.Height. 76. 8 Force.You can also interactively use Set Display.Resolution by simply typing the command.It will ask for a value for Width and Height.It will then change the resolution.You can either accept it with Y or revert to the previous screen resolution by typing N.Activating Server Core When youve successfully configured your Server Coreinstallation, and you have the feeling you wont be able to mess up its core configuration, its time to activate it.When youve implemented Key Management Services KMS or Active Directory based Activation, your installation might already be activated and you dont need to activate it at the command line.If you do want to activate the installation at the command line, use the following commands.Slmgr. vbs ipk THISI SNOTA LEGIT PRODU CTKEY1.Slmgr. vbs ipk THISI SNOTA LEGIT PRODU CTKEYTo check whether your. Install Gns3 Qemu On Ubuntu Server on this page. Server Core installation activated correctly, use slmgr.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |