How to perform licensing for Windows Server 2008 R2 via KMS server

How to perform licensing for Windows Server 2008 R2 via KMS server

Execute below steps from – Command Prompt, Ensure space

 

slmgr /ipk KEY of your product

slmgr /skms  KMS Server IP 

slmgr /ato

 

How to find the members of Local Groups in Windows Server 2008 R2

Easy way to get the details of your local groups on Windows Server 2003 & 2008 R2

Go to – Command prompt 

Type :- net localgroup “GroupName”

see below :-

 

How to sync server time with Domain Controller

Hello People,

If you wish to synchronize your server time with its respective Domain controller, You can always do it with the help of Command Prompt.

Ideally Windows Time Services does this automatically, however because of any reason If you see that there is a time difference, feel free to run below command on Server using Command Prompt.

To run this command you need to be a part of Domain Admin group on Active Directory

Steps as below :-

1. Open cmd, right click & say "Run As Administrator"
2. Type below mentioned command 

You'll be notified with the time and success of this command with its output.

I thank you for your time

Happy learning

How to find group membership of a user on Active Directory

Hello People,

If you wish to find the groups, related to any user Active Directory profile, You can of course use GUI and check the groups on ADCU (Active Directory Users & Computers).

However there is another way, using command line tool, you need to be a part of Domain Administrator & logon to Domain Controller to perform & find the results of below command

1.  Please open CMD - command prompt
2. Type - dsquery user -samid (userid) | dsget user -memberof
3. Typing - dsquery user -samid (bhandyal) | dsget user -memberof  >> abc.txt - Will save text file on your root drive.

I've tested this on many of my DCs & found successful results.
Please ensure, that the above command is space sensitive, If not working for you, Please ensure, you are entering correct space.

Thanks

Happy to help

How to find user SID - Command Line

Hi People,

You can simply run this command on Server - 2003 & 2008 R2 editions to get the Users Romaing profile SID.

wmic useraccount where name='username' get sid

Say enter, once type this in command line.

There are couple of other Links related to User profile Issue, as below

http://support.microsoft.com/kb/154599

http://support.microsoft.com/?kbid=947242

http://support.microsoft.com/kb/947215

Thanks for your time
Happy to help

Citrix Issues ICA listener / session down

Hi People,




We encounter this issue many times, when running on Citrix environments, especially when we do not reboot our Citrix server ever after 14 days, ideally recommended to bounce citrix server once in 14 days.

We have port 1494 – which holds the listener & respond to Citrix gateway & application is pulled from application server, this all can be managed from Citrix Management Console (CMC)

Steps to check & reset down session / ICA listener:-

 Please logon to Citrix server, Can use Citrix website, for reference

 Launch Citrix Management Console

 Check for the alerts raised on CMC

 Browse Application on CMC & select application, which has issue

 Change Display (in The middle Pane) to Session

 At your left hand side, You’ll see several session, Search & locate “down”

 Select “down” & right click perform “reset”

 Once done from CMC, go to Terminal Server Services (tsadmin)

 Select the server local or can connect to the another Citrix server in the farm

 At left hand side, search & locate “down” ICA listener, right click & say reset

 Doing it from Terminal Server is fast & effective

 Have the requestor to test the application, Issue will be resolved



Happy Learning, I thank you for your valuable time

 

route add command in windows server

Hi People,




We come across the situation, where we have to define route on windows servers, defining routes would be (Print / Add / Delete & Change)

Switches: -

 -p (Added the route to windows server registry, without p it will store the route to RAM-based IP routing table, this option without p is used very rarely

 -f (Clears the routing table of all gateway entries)

Route Commands:-



 route print (destination IP address) :- Will print the route of the destination IP address

 route add –p abc mask xyz pqr IF 15 :- Where (abc – IP to be routed, xyz – Subnet mask, pqr – gateway of the windows server, 15 – Interface)

 route delete (destination IP address) :- This will delete the route of the specified destination

 route change :- Changes the route (Please use similar values, as in route add )

 route mask (netmask) :- It specifies the next parameter of the next mask value, If nothing is provided, by default it takes 255.255.255.255)

Ideally Network admins deals with these things, however good to know information for Windows Admin, if they encounter any issues with route



Happy learning, I thank you for your valuable time

Unable to open websites, using newly added (bind) IP address on server 2008 R2, Using IIS

Hi people,



If you come across a situation, where your newly added (Bind) IP address are not responding on IIS, this could be related to several issue, as below

 DNS Records Issue – Check DNS server & verify records are resolving properly, use nslookup utility, If required perform flushdns, to have fast results

 Telnet port 80 or 443, using newly added IP address – Open cmd – telnet X.X.X.X 80, look for the result & act accordingly

 If you are getting – connection could not be established on telnet, for those IP address, it means that IP is not listened on port 80- by IIS, to check this, you can also type the IP address in browser and see, what it brings up, act accordingly

 If there is no blockage on Firewall – Both Windows & Network, you have to make IP listen forcefully, use below command



netsh http add iplisten 10.X.X.X



 After performing this command, you can telnet to the required port & it will have th IP up on that port, for 443, make sure, you have SSL & proper cert attached to the web site.



Please feel free to raise your questions on this



Happy Learning & I thank you for your valuable time

Some scripts

Scripts to check number of users under different CN & OU

dsget group "CN=ctxapp,OU=Production,OU=SDS,OU=Groups,OU=Citrix,DC=abc, DC=xyz, DC=123" -members > File name .csv

Scripts to check disable user on AD

dsquery user -name "user name" | dsmod user -disabled yes

Run these on command prompt

The general steps to migrate from Windows Server 2000 to Windows Server

Scenario:




Old server: Windows Server 2000 box

New server: Windows Server 2008 box



1. Verify that Windows 2000 SP4 have been installed on the old server and

Windows Server 2008 SP1 have been installed on the new server



Note: the domain functional level should be in Windows 2000 native mode for

the Windows 2000 domain.



2. Upgrade the Windows 2000 forest schema by running "adprep /forestprep"

command on old server



Note: you can copy the adprep folder from the Windows Server 2008

installation disc to the old server to run "adprep /forestprep".

The location is \source\adprep on the installation disc.



3. Upgrade the Windows 2000 domain schema by running "adprep /domainprep"

command on old server



4. Verify the new server's TCP/IP configuration has been pointed to

existing DNS server.



5. Add new server to existing Windows 2000 domain as a member server.



6. Run dcpromo on new server to promote it as an additional domain

controller in existing Windows 2000 domain, afterwards you may verify the

installation of Active Directory.



7. Enable Global Catalog on new server and manually Check Replication

Topology and afterwards manually trigger replication to synchronize Active

Directory database between 2 replica.



8. Disable Global Catalog on old server.



9. Use NTDSUTIL utility to transfer all the 5 FSMO roles from old server to

new server. You'd better transfer FSMO roles via GUI method instead of

using NTDSUTIL.



10. Install DNS component on new server and configure it as a new DNS

Server(Active Directory Integrated-Zone is preferred)



Note: all the DNS configuration need to be transferred from the existing

DNS Server.



11. Migrate DHCP service from Windows Server 2000 to Windows Server 2008



Please refer to:

How to move a DHCP database from a computer that is running Windows NT

Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is

running Windows Server 2003

http://support.micro....aspx/kb/325473

(This should work on Windows Server 2008)



12. Migrate File Sharing service from



You can also use robocopy.exe from the Windows Server Resource kit to copy

the files and maintain NTFS permissions.



For the shares, the shares definitions and permissions are stored in the

following registry key on the server:



HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanserver\Shares



If you export out the whole key and import in the new server, and if you

have the files and folders in the same path as in the old server, then you

will retain all you shares and share permissions.



12. It's better to make the old DC offline for several days and check

whether everything works normally with the new server online. If so, you

may let the old DC online and run DCPROMO to demote it.



For more information, please refer to:



Identifying Your Windows Server 2008 Functional Level Upgrade

http://technet2.micr....03a77-d9ba-4a2

6-b756-eba5499f15581033.mspx?mfr=true



How To Install and Configure DNS Server in Windows Server 2003

http://support.micro...b/814591/EN-US/



How To Convert DNS Primary Server to Active Directory Integrated

http://support.microsoft.com/kb/816101

What is GRUB & How is Works

GRUB :- GRand Unified Bootloader


GNU GRUB is a bootloader (can also be spelled boot loader) capable of loading a variety of free and proprietary operating systems. GRUB will work well with Linux, DOS, Windows, or BSD. GRUB stands for GRand Unified Bootloader.




GRUB is dynamically configurable. This means that the user can make changes during the boot time, which include altering existing boot entries, adding new, custom entries, selecting different kernels, or modifying initrd. GRUB also supports Logical Block Address mode. This means that if your computer has a fairly modern BIOS that can access more than 8GB (first 1024 cylinders) of hard disk space, GRUB will automatically be able to access all of it.



GRUB can be run from or be installed to any device (floppy disk, hard disk, CD-ROM, USB drive, network drive) and can load operating systems from just as many locations, including network drives. It can also decompress operating system images before booting them.

How does GRUB work?


When a computer boots, the BIOS transfers control to the first boot device, which can be a hard disk, a floppy disk, a CD-ROM, or any other BIOS-recognized device. We'll concentrate on hard disks, for the sake of simplicity.



The first sector on a hard is called the Master Boot Record (MBR). This sector is only 512 bytes long and contains a small piece of code (446 bytes) called the primary boot loader and the partition table (64 bytes) describing the primary and extended partitions.



By default, MBR code looks for the partition marked as active and once such a partition is found, it loads its boot sector into memory and passes control to it.



GRUB replaces the default MBR with its own code.



Furthermore, GRUB works in stages.



Stage 1 is located in the MBR and mainly points to Stage 2, since the MBR is too small to contain all of the needed data.



Stage 2 points to its configuration file, which contains all of the complex user interface and options we are normally familiar with when talking about GRUB. Stage 2 can be located anywhere on the disk. If Stage 2 cannot find its configuration table, GRUB will cease the boot sequence and present the user with a command line for manual configuration.



Stage 1.5 also exists and might be used if the boot information is small enough to fit in the area immediately after MBR.



The Stage architecture allows GRUB to be large (~20-30K) and therefore fairly complex and highly configurable, compared to most bootloaders, which are sparse and simple to fit within the limitations of the Partition Table.

GRUB :- GRand Unified Bootloader

GNU GRUB is a bootloader (can also be spelled boot loader) capable of loading a variety of free and proprietary operating systems. GRUB will work well with Linux, DOS, Windows, or BSD. GRUB stands for GRand Unified Bootloader.

GRUB is dynamically configurable. This means that the user can make changes during the boot time, which include altering existing boot entries, adding new, custom entries, selecting different kernels, or modifying initrd. GRUB also supports Logical Block Address mode. This means that if your computer has a fairly modern BIOS that can access more than 8GB (first 1024 cylinders) of hard disk space, GRUB will automatically be able to access all of it.

GRUB can be run from or be installed to any device (floppy disk, hard disk, CD-ROM, USB drive, network drive) and can load operating systems from just as many locations, including network drives. It can also decompress operating system images before booting them.



How does GRUB work?

When a computer boots, the BIOS transfers control to the first boot device, which can be a hard disk, a floppy disk, a CD-ROM, or any other BIOS-recognized device. We'll concentrate on hard disks, for the sake of simplicity.

The first sector on a hard is called the Master Boot Record (MBR). This sector is only 512 bytes long and contains a small piece of code (446 bytes) called the primary boot loader and the partition table (64 bytes) describing the primary and extended partitions.

By default, MBR code looks for the partition marked as active and once such a partition is found, it loads its boot sector into memory and passes control to it.

GRUB replaces the default MBR with its own code.

Furthermore, GRUB works in stages.

Stage 1 is located in the MBR and mainly points to Stage 2, since the MBR is too small to contain all of the needed data.

Stage 2 points to its configuration file, which contains all of the complex user interface and options we are normally familiar with when talking about GRUB. Stage 2 can be located anywhere on the disk. If Stage 2 cannot find its configuration table, GRUB will cease the boot sequence and present the user with a command line for manual configuration.

Stage 1.5 also exists and might be used if the boot information is small enough to fit in the area immediately after MBR.

The Stage architecture allows GRUB to be large (~20-30K) and therefore fairly complex and highly configurable, compared to most bootloaders, which are sparse and simple to fit within the limitations of the Partition Table.

GRUB :- GRand Unified Bootloader

GNU GRUB is a bootloader (can also be spelled boot loader) capable of loading a variety of free and proprietary operating systems. GRUB will work well with Linux, DOS, Windows, or BSD. GRUB stands for GRand Unified Bootloader.

GRUB is dynamically configurable. This means that the user can make changes during the boot time, which include altering existing boot entries, adding new, custom entries, selecting different kernels, or modifying initrd. GRUB also supports Logical Block Address mode. This means that if your computer has a fairly modern BIOS that can access more than 8GB (first 1024 cylinders) of hard disk space, GRUB will automatically be able to access all of it.

GRUB can be run from or be installed to any device (floppy disk, hard disk, CD-ROM, USB drive, network drive) and can load operating systems from just as many locations, including network drives. It can also decompress operating system images before booting them.



How does GRUB work?

When a computer boots, the BIOS transfers control to the first boot device, which can be a hard disk, a floppy disk, a CD-ROM, or any other BIOS-recognized device. We'll concentrate on hard disks, for the sake of simplicity.

The first sector on a hard is called the Master Boot Record (MBR). This sector is only 512 bytes long and contains a small piece of code (446 bytes) called the primary boot loader and the partition table (64 bytes) describing the primary and extended partitions.

By default, MBR code looks for the partition marked as active and once such a partition is found, it loads its boot sector into memory and passes control to it.

GRUB replaces the default MBR with its own code.

Furthermore, GRUB works in stages.

Stage 1 is located in the MBR and mainly points to Stage 2, since the MBR is too small to contain all of the needed data.

Stage 2 points to its configuration file, which contains all of the complex user interface and options we are normally familiar with when talking about GRUB. Stage 2 can be located anywhere on the disk. If Stage 2 cannot find its configuration table, GRUB will cease the boot sequence and present the user with a command line for manual configuration.

Stage 1.5 also exists and might be used if the boot information is small enough to fit in the area immediately after MBR.

The Stage architecture allows GRUB to be large (~20-30K) and therefore fairly complex and highly configurable, compared to most bootloaders, which are sparse and simple to fit within the limitations of the Partition Table.

How does GRUB work?


When a computer boots, the BIOS transfers control to the first boot device, which can be a hard disk, a floppy disk, a CD-ROM, or any other BIOS-recognized device. We'll concentrate on hard disks, for the sake of simplicity.



The first sector on a hard is called the Master Boot Record (MBR). This sector is only 512 bytes long and contains a small piece of code (446 bytes) called the primary boot loader and the partition table (64 bytes) describing the primary and extended partitions.



By default, MBR code looks for the partition marked as active and once such a partition is found, it loads its boot sector into memory and passes control to it.



GRUB replaces the default MBR with its own code.



Furthermore, GRUB works in stages.



Stage 1 is located in the MBR and mainly points to Stage 2, since the MBR is too small to contain all of the needed data.



Stage 2 points to its configuration file, which contains all of the complex user interface and options we are normally familiar with when talking about GRUB. Stage 2 can be located anywhere on the disk. If Stage 2 cannot find its configuration table, GRUB will cease the boot sequence and present the user with a command line for manual configuration.



Stage 1.5 also exists and might be used if the boot information is small enough to fit in the area immediately after MBR.



The Stage architecture allows GRUB to be large (~20-30K) and therefore fairly complex and highly configurable, compared to most bootloaders, which are sparse and simple to fit within the limitations of the Partition Table.

GRUB :- GRand Unified Bootloader

GNU GRUB is a bootloader (can also be spelled boot loader) capable of loading a variety of free and proprietary operating systems. GRUB will work well with Linux, DOS, Windows, or BSD. GRUB stands for GRand Unified Bootloader.

GRUB is dynamically configurable. This means that the user can make changes during the boot time, which include altering existing boot entries, adding new, custom entries, selecting different kernels, or modifying initrd. GRUB also supports Logical Block Address mode. This means that if your computer has a fairly modern BIOS that can access more than 8GB (first 1024 cylinders) of hard disk space, GRUB will automatically be able to access all of it.

GRUB can be run from or be installed to any device (floppy disk, hard disk, CD-ROM, USB drive, network drive) and can load operating systems from just as many locations, including network drives. It can also decompress operating system images before booting them.



How does GRUB work?

When a computer boots, the BIOS transfers control to the first boot device, which can be a hard disk, a floppy disk, a CD-ROM, or any other BIOS-recognized device. We'll concentrate on hard disks, for the sake of simplicity.

The first sector on a hard is called the Master Boot Record (MBR). This sector is only 512 bytes long and contains a small piece of code (446 bytes) called the primary boot loader and the partition table (64 bytes) describing the primary and extended partitions.

By default, MBR code looks for the partition marked as active and once such a partition is found, it loads its boot sector into memory and passes control to it.

GRUB replaces the default MBR with its own code.

Furthermore, GRUB works in stages.

Stage 1 is located in the MBR and mainly points to Stage 2, since the MBR is too small to contain all of the needed data.

Stage 2 points to its configuration file, which contains all of the complex user interface and options we are normally familiar with when talking about GRUB. Stage 2 can be located anywhere on the disk. If Stage 2 cannot find its configuration table, GRUB will cease the boot sequence and present the user with a command line for manual configuration.

Stage 1.5 also exists and might be used if the boot information is small enough to fit in the area immediately after MBR.

The Stage architecture allows GRUB to be large (~20-30K) and therefore fairly complex and highly configurable, compared to most bootloaders, which are sparse and simple to fit within the limitations of the Partition Table.

The remote session was disconnected because there are no remote desktop license servers available to provide a license

1.      Login to a server of same vlan.

2.      Click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.

 

3.      If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click yes. 

4.      Under Licensing, double-click Remote Desktop license servers. 

5.      In the Remote Desktop license servers area, click Add. 

6.      In the License sever name or IP address box, type the server name or IP address of the Remote Desktop license server. 

7.      Click OK, and then click OK again.

Verify

To verify that connections to the RD Session Host server are working properly, establish a remote session with the RD Session Host server.