Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, March 31, 2014 2:55 PM
Symptom
When you install the Telnet Server feature on a Windows Server 2012 R2 Server Core machine using the Install-WindowsFeature cmdlet, you may face the issue that the installation process hangs at 68% (Figure 1).
Figure 1: Installation hang at 68%
When we insert the installation disk on the machine and specify that the source of feature files for the installation, the process still can’t go beyond 68% (Figure 2).
Figure 2: Installation still hangs at 68%
Analysis
Since the installation stops even if we specify the source of feature files on the disk or image, we should first verify available Windows features in the image. When using Dism /online /Get-Features cmdlet to list all of available features on the system, we found that the state of TelnetServer feature shows: Disabled with Payload Removed. In addition, the output result also shows the state of TFTP feature is Disabled with Payload Removed and the same issue occurs while installing TFTP feature (Figure 3).
Figure 3: The TelnetServer feature is disabled with Payload Removed
When we install the feature using a WIM image with the following cmdlet Install-WindowsFeature <featurename> -Source wim:<path>:<index>, the installation still can’t go beyond 68% (Figure 4).
Figure 4: Installation of the TFTP-Client feature still hangs at 68%
The state “Disabled with Payload Removed” means the feature payload was removed from Windows Server 2012 image. Since Telnet Server feature is supported by Windows Server 2012 R2 Server Core, it should be included in the image. If we choose an unsupported feature such as Windows Deployment Services, the output will directly show that this is not an invalid feature (Figure 5).
Figure 5: Invalid Feature
According to the above, we can conclude that the source file is missing in the image.
**
Workaround**
Based on the conclusion, we could try to enable Telnet Server feature using DISM cmdlet: Dism /online /Enable-Feature /FeatureName:TelnetServer /All
Also, we could specify the source path with correct index number while installing it using DISM:
Dism /online /Enable-Feature /FeatureName:TelnetServer /All /Sources:D:\Sources\install.wim:4
***Note:***Please make sure to use the index of the image for the Server with a GUI version of Windows Server 2012 R2
After finishing running the command, we could found the state of TelnetServer shows Enabled when issuing Dism /Online /Get-Features (Figure 6). And the Telnet Server feature will be installed successfully when we run Get-WindowsFeature cmdlet to retrieve information about features on this machine (Figure 7).
Figure 6: Telnet Server is installed (DISM)
Figure 7: Telnet Server is installed (Get-WindowsFeature)
Then you can confirm it by running “tlntadmn” cmdlet and telnet service can be configured (Figure 8).
Figure 8: Verify the Telnet Server working properly
Useful Links
Install Server Roles and Features on a Server Core Server
http://technet.microsoft.com/en-us/library/jj574158.aspx
Enable or Disable Windows Features Using DISM
http://technet.microsoft.com/en-us/library/hh824822.ASPX
Tlntadmn
http://technet.microsoft.com/en-us/library/ff698995.aspx
If you need further assistance, welcome to post questions in our Server Core forum.
Keyword: Server Core, install TelnetServer
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.