Windows – ‘Telnet’ is not recognized as an internal or external command

KB ID 0000455

Problem

Telnet client from Windows, and have it as an “Optional Extra”. For most people that’s fine, but for anyone who programs network devices, or needs to test that ports are open, or test mail flow by telnet to port 25, that’s a pain.

Solution

Enabling Telnet – Windows 10

1. From PowerShell execute the following command;

[box]

dism /online /Enable-Feature /FeatureName:TelnetClient

[/box]

Enabling Telnet – Windows Server 2019, 2016, and 2012

1. From PowerShell execute the following command;

[box] Add-WindowsFeature Telnet-Client [/box]

Enabling Telnet – Windows 8, 7, Vista, and Server 2008 (NOT R2)

1. Open a command Window and execute the following command;

[box] pkgmgr /iu:"TelnetClient" [/box]

Or

2. Control Panel > Programs > Turn Windows features on or off > Select “Telnet Client” > OK.

Note: On Windows 8, Press Windows Key+X to get straight to control panel.

Enabling Telnet – Windows Server 2008 R2

1. From command line execute the following command;

[box] servermanagercmd -i telnet-client [/box]

Or

2. Launch Server Manager > Features > Add Features > Locate and select “Telnet Client”.

 

Related Articles, References, Credits, or External Links

NA

Windows Update Error C8000710

KB ID 0000769 

Problem

Seen when attempting to perform windows update.

Solution

If you didn’t already know, then your problems have just got bigger, this error indicates there’s not enough room on the drive.

Find Out What’s Filled up the Hard Drive

Related Articles, References, Credits, or External Links

NA

Add a 2012 Domain Controller to a 2008 Domain

KB ID 0000680 

Problem

This is considerably less painfull than adding a 2008/2008 R2 domain controller to a 2003 domain was. You dont have to maually prep the schema on the schema master, or run forestprep and domainprep. The wizard does everything for you.

Solution

1. Launch server manager from the taskbar > Select Local Server > Manage > Add Roles and Features.

2. Role Based… > Next.

3. Select local server > Next.

4. Tick ‘Active Directory Domain Service’ > Next.

5. Accept the defaults > Next.

6. Next.

7. Install.

8. Installation may take a while.

9. When finished nothing appears to change, but it does say “Suceeded” > Close.

10. Now the role is on the server you just need to promote it, you can do this by selecting AD DS in the left hand menu > and click ‘More’.

11. ‘Promote the server to a domain controller’

12. By default it will fill in the domain you are already a member of > Next

13. Enter your directory servies restore mode password (DON’T ever lose this password!) > Next.

14. I dont want anyone outside my domain browsing my domain so I don’t care about the delegation error > Next.

15. If you want to reboot as soon at it’s finished tick the box, and (optionally) select a Dc to replicate from > Next.

16. Accept or change the paths as required > Next.

17. Heres a nice touch, now it preps the forest, schema, and domain for you > Next.

18. Next.

19. Install (I’d suggest a reboot when its done).

Related Articles, References, Credits, or External Links

NA

Windows Server – Fine Grained Password Policies

KB ID 0000765 

Problem

Before server 2008 if you wanted more than one password policy, you had to create a sub domain just to do that! with Server 2008 we were given fine grained password policies, which were fine (if a little clunky), and involved you creating ‘Password Settings Objects’.

They were a pain if you were not used to them e.g. five minutes is entered as 00:00:05:00. But now Microsoft have made things a LOT EASIER (though they made a good job of hiding it!).

Solution

1. From Server Manager (ServerManager.exe) > Local Server > Tools > Active Directory Administrative Center.

2. System container.

3. Password Settings Container.

4. New > Password Settings > Configure as required > Add > Locate the Security group you want to apply the policy to > OK > OK.

Note: The Precedence dictates which policy will apply if the same user has multiple policies applied to them.

5. You can then create other policies to apply to different groups.

To See What Policies are Applying to a User

6. Locate the user (while still in Active Directory Administrative Center) Right click > View resultant password settings > If a policy is in place it will open.

7. If there is no policy in place you will see, “User does not have resultant fine grained password settings. Please check the user’s domain password settings”.

 

Related Articles, References, Credits, or External Links

NA

Windows Server 2012 and Windows 8 – Activation Error 0xC004F074

KB ID 0000766

Problem

I jumped on a clients remote desktop services server today and saw;

However when I went to activate;

Windows couldn’t be activated
Error Code: 0xC004F074
Error Description:the Software Licensing Service reported that the product could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.

Solution

Out of the box this version of Windows has installed with a KMS Key, that’s fine if you are going to run KMS, here’s how to set it up. But if you want to activate with MAK key or a retail key then you need to manually change it.

1. Press Windows Key+R > cmd {enter} and execute the following command;

[box]
slmgr.vbs /ipk 12345-ABCDE-12345-ABCDE-12345[/box]

Where 12345-ABCDE-12345-ABCDE-12345 is your MAK or retail key

2. Now attempt to activate the machine again,

Note: You can also activate by running the following command;

[box] slmgr.vbs -ato[/box]

Related Articles, References, Credits, or External Links

Windows 8 – Changing the Unlock Code and Activating

Windows Server 2012 – RDP Server – How to get the ‘Start / Metro Screen’

KB ID 0000767

Problem

When you RDP to a server running Windows Server 2012, in Remote Desktop Services (Terminal Server) mode. How do you get the start menu up? If you press the Windows Key or Ctrl+Esc, you get the menu on YOUR Machine?

Solution

Firstly, I know it’s not called the ‘Metro Interface’ any more, but that’s what everyone calls it!

1. Drag your mouse pointer off the bottom left hand side of the screen (1) and a thumbnail of the start menu will appear (2).

2. Move the mouse pointer back to the thumbnail (3) this takes a little practice, then click the start menu thumbnail (4).

To shutdown or log off (disconnect) use the same method as you would for Windows 8 (using the charms bar).

UPDATE 04/11/13 (Credit to Thomas Dread)

1. Windows Key +R > mstsc {Enter}.
2. Show Options.
3. Local Resources TAB.
4. Keyboard > Apply Windows Key combinations “On the Remote Computer” drop down menu.

5. Back to General TAB.
6. Save or Save AS.

How Do I Shut Down Windows 8?

Related Articles, References, Credits, or External Links

NA

Remote Desktop Services – RemoteApp Error ‘The remote computer could not be found. Please contact your helpdesk about this error’

KB ID 0000768

Problem

While attempting to launch a web app from a Windows Server 2012 Remote Desktop Services (Terminal) server. Clients were greeted with the following;

RemoteApp Disconnected The remote computer could not be found. Please contact your helpdesk about this error.

Solution

1. On the Server, Start > RD Gateway Manager > Locate your server > right click > properties > Server farm > Type in the FQDN of the server* (Your remote clients must be able to resolve this name!) > Add > Make sure it gets listed as ‘OK’ > Apply > OK.

*Note: This assumes you have one RDS server, if you have many then obviously enter the FQDN of the one fulfilling the RD Gateway role.

2. Start > Internet Information Services (IIS) Manager > Expand the server > Sites > Default Web Site > RDWeb > Pages > Application Settings.

3. Open DefaultTSGateway > Set its value to the FQDN of the RD Gateway server (as above) > OK.

4. Finally restart IIS with an iisreset command.

Related Articles, References, Credits, or External Links

NA