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
Thursday, August 20, 2015 9:48 AM | 1 vote
Hi,
I have problem with DHCP after I was install RSAT package WindowsTH-KB2693643-x86.msu.
Installation was complete without any error but when I turn on all RSAT features and roles DHCP feature for some reasons missing in administrative tools and mmc snap in options. After that I am turn off only DHCP in control panel (Turn windows features on or off) and again turn on but without success.
I was upgrade windows 8.1 to windows 10 earlier without any problems.
Any suggestions??
All replies (37)
Thursday, August 20, 2015 10:33 AM ✅Answered | 4 votes
Read the details for the RSAT download:
Remote Server Administration Tools for Windows 10 can be used to manage roles and features that are running on Windows Server Technical Preview, with the following exceptions:
- DHCP Tools.* Dhcpmgmt.msc is not available in this release of RSAT, but equivalent Windows PowerShell cmdlets are available.*
- IP Address Management (IPAM) Tools. IPAM tools are not available in this release of RSAT.
- Network Policy Server Tools. The NPS console is not supported on a Windows client-based operating system, and will be removed from future releases of RSAT.
- Routing and Remote Access Tools. Routing and Remote Access Tools that are GUI-based cannot be used for remote configuration in this release of RSAT, but the equivalent Windows PowerShell cmdlets are available.
Hope that helps!
Thursday, August 20, 2015 10:55 AM
Thank you.
Friday, August 21, 2015 9:23 PM | 2 votes
You did not think you were going to get a release from Microsoft that had "everything" working , did you??? I mean you had to wait for this release because they thought releasing the Enterprise version for W10 without all the tools was a wise decision.
And after waiting they release a tool with missing features, great bunch always have been.
Monday, August 24, 2015 1:18 PM
Why were DHCP tools not included? Most of the time I use them just to find an IP address for one of my users, and not to make changes to DHCP, although that is very useful.
Monday, August 24, 2015 2:54 PM
My guess is that in Windows Server 2016 the console gets an update (GUI over PowerShell back-end) and is incompatible with older DHCP servers. When the RTM version of Server 2016 is released, we'll get an update for RSAT.
Tuesday, August 25, 2015 8:55 AM | 1 vote
You did not think you were going to get a release from Microsoft that had "everything" working , did you??? I mean you had to wait for this release because they thought releasing the Enterprise version for W10 without all the tools was a wise decision.
And after waiting they release a tool with missing features, great bunch always have been.
Me too !
And when you go to update your Icon.. They are sooo ugly on the StartScreen.
:(
Thursday, August 27, 2015 1:30 PM | 3 votes
Another suggestion although not supported would be to copy dhcpmgmt.msc and dhcpsnap.dll from a Windows 2012 box from the Windows\System32 folder onto the Windows 10 System32 folder. Then register the dhcpsnap.dll.
regsrv32 dhcpsnap.dll
Friday, August 28, 2015 1:19 AM
I tried that and it opened the snap in but with many errors and you cannot add server, any one confirm that actually works?
Wednesday, September 2, 2015 3:48 AM
This doesn't work ! :(
Windows 10 Enterprise
Tuesday, September 8, 2015 1:36 PM
Tried that registered the dll OK but cannot add the MSC
error is " cannot initialize the snap in"
any ideas out there?
Friday, September 11, 2015 1:06 PM | 5 votes
This doesn't work ! :(
Windows 10 Enterprise
I'm using Win 10 x64 and it's working....
Don't forget to run CMD as administrator and to copy the dhcpsnap.dll.mui into %systemroot%\System32\en-US\
HTH
Thursday, September 17, 2015 2:24 PM | 1 vote
works great thanks! Win 10 x64 enterprise
Friday, September 18, 2015 8:59 AM
I second this, copying, registering - it works. odd enough we had the files in en-US folder already there...
Wednesday, September 23, 2015 7:23 PM
This and what hyperlite suggest will solve the problem, or at least it does for me in Win10x64. Thanks guys!
Thursday, September 24, 2015 12:37 PM | 1 vote
I had to run "regsvr32 dhcpsnap.dll" in CMD.. Not "regsrv32 dhcpsnap.dll"
The rest is OK though.
Take ownership of the files/folder in C:\windows\system32 and then you can replace the one in EN-US.
Thanks all for your help!
Thursday, September 24, 2015 10:27 PM
You SHOULD be able to get the same information from the Dns manager as well. Server -> Forward Lookup zones -> (internal domain. Gives me a full list of device name / record type / IP address / static address or renewal time stamp.
Monday, October 5, 2015 6:37 PM
I'm still having the "MMC cannot initialize the snap-in" error when I try to do this process? Is everyone else getting this to work? Or are others still having the issue as well?
Thanks,
Mike
Mike
Wednesday, October 7, 2015 5:58 PM
I had to run "regsvr32 dhcpsnap.dll" in CMD.. Not "regsrv32 dhcpsnap.dll"
The rest is OK though.
Take ownership of the files/folder in C:\windows\system32 and then you can replace the one in EN-US.
Thanks all for your help!
Thank You so much! Works here perfectly. I just have to copy the dhmgmt.msc and dhcpsnap.dll from System32 and the same files from System32\pt-BR. Copy to the same folders and register it. Thanks!
Friday, October 9, 2015 9:19 AM
This totally does not work have no idea what everyone is stating in this thread. Still awaiting some DHCP option for Windows 10
Friday, October 9, 2015 9:25 AM
It does work mate, I'm using it now - what problem are you having?
Friday, October 9, 2015 12:30 PM
I'm with dudleydogg... Still getting "MMC Cannot initialize the snap-in".
I'm running Windows 10, build 10240.
Mike
Friday, October 9, 2015 2:07 PM
Works fine for me too. you have to copy and register the dhcpsnap.dll in win\system32 after copying the files to win\system32\en-us.
Friday, October 9, 2015 2:31 PM
Did you copy the files from a Win 7 machine? Or from a Server 2012 machine?
Thanks,
Mike
Mike
Friday, October 9, 2015 2:34 PM | 4 votes
They were copied from a 2012 server. Coincidentally, from one of our DHCP servers.
Just to clarify the process that worked for me:
1. copy dhcpmgmt.msc and dhcpsnap.dll.mui from system32\en-us on the 2012 server to the same location on the w10 pc (this may not be needed. the files already exist)
2. copy dhcpsnap.dll from system32 on the 2012 server to the w10 pc
3. regsvr32.exe dhcpsnap.dll in system32
4. open mmc and load the dhcp snap-in
Friday, October 9, 2015 2:49 PM
Our DHCP servers are still 2008... Wonder if those will work too?
Mike
Friday, October 9, 2015 2:54 PM
I couldn't answer that, but if you had a 2012 server handy I would use that instead. I just happened to use one of our dhcp servers because it was the first 2012 server that came to mind in our environment.
Friday, October 9, 2015 4:31 PM
Thank you mkuhnbbmc! I think step 4 was what did it!
4. open mmc and load the dhcp snap-in
One of the instructions I had read said create a shortcut to dhcpmgmt.msc, which is what I had done and that wasn't working. Once I added it in from MMC, it WORKED! I did end up re-copying from a 2012 server to my Windows 10 machine just to make sure I had the right ones.
Thanks again!
Mike
Mike
Monday, October 12, 2015 5:56 PM
This was a great solution, I followed the steps posted by mkuhnbbmc and it works great. It was very frustrating to have to log into the server anytime I wanted to look up something in DHCP, now I don't have to bother with it.
Monday, October 12, 2015 8:00 PM
The copy and register of the DLL works.
Thank you!
Thursday, October 15, 2015 8:54 PM
Hello
For french or other nationality users. this method didn't work for me because i copied dll and dhcpmgmt.msc from a french edition of windows server 2012r2. Solution was installed en-US language pack on server and use mkuhnbbmc method. It works like a charm.
you can personalize adding the dhcp mmc on a tile. create shortcut on desktop (%SystemRoot%\system32\mmc.exe %SystemRoot%\system32\en-US\dhcpmgmt.msc) and copy this shorcut on admintools folder. To retrieve original icon, clic on the shorcut property and "change icon", and find dhcpsnap.dll file in system32 folder. It's done.
Thanks to all persons on this post
Thursday, October 22, 2015 8:09 AM | 2 votes
Here is the whole workaround as shown above but step by step. Copying the files is needed no matter older versions exists!
1. Frist copy dhcpmgmt.msc and dhcpsnap.dll from a Windows 2012 server %systemroot%\System32 folder onto the Windows 10 System32 folder.
2. Then you need to copy dhcpsnap.dll.mui from a Windows 2012 server %systemroot%\System32\en-US into the %systemroot%\System32\en-US\ on your Win10 computer. Unfortunately you don’t have permissions to do that by default. So to do it take ownership of C:\Windows\System32\en-US and give yourself permission, and copy the file. After copying the file reverse the permissions back to the defaults (just in case) – remove the permission you gave yourself and then give back TrustedInstaller the ownership by adding "NT SERVICE\TrustedInstaller" as owner.
3. As a last step you need to register the dhcpsnap.dll as shown below.
Run CMD as Administrator and type: regsvr32 dhcpsnap.dll
Friday, October 23, 2015 7:07 PM
Our DHCP servers are still 2008... Wonder if those will work too?
Mike
Server 2008R2 source and Windows 10 Pro x64 worked great here.
Monday, October 26, 2015 9:29 PM
Yes, this work for me to! Copy the files from 2008 R2 server as Vaskodd described and worked like a charm!
So if you have windows 2016 / 2012 / 2008 this method should work.
Thanks everyone for the help!
Tuesday, November 17, 2015 6:18 PM
Perfect. It works fine for me.
Thank you.
Thursday, November 19, 2015 11:43 PM
*** Don't Worry, i'd found it had moved one of the files to C:\Windows.old\Windows\System32 ***
Moved it back and all working again.
****Old****
I've just updated to Windows 10 Build 1511 and can no longer get the DHCP MMC add-in to work.
DHCP MMC was working with initial release of windows 10. I've re-installed the RSAT for Windows 10 pack, done the steps of coping the files as mentioned again, but when going to register the dll file I get the following error;
The module "dhcpsnap.dll" may not compatible with the version of Windows that you're running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe
I've tried both the x64 and x86 version of regsvr32.exe, even moved the DLL to the SysWoW64 folder. No luck any way,
Is there newer files I need with this build of windows or RSAT (KB2693643)
Any help?
Friday, May 20, 2016 9:33 PM
We have created a DHCP Console for Windows 10, well, not created as such but its an installer that works around it not being in RSAT for Windows 10. Basically you run the installer and the DHCP appears on your desktop to use on Windows 10.
See here for details:
http://blog.techygeekshome.info/2016/05/dhcp-console-for-windows-10/
Hope it helps.
http://blog.techygeekshome.info
Friday, May 20, 2016 9:36 PM | 1 vote
weird,.. seeing as of atleast a month ago dhcp has been installing with the rest of it for me.
I am using the following powershell script, makes it easy since I am on the insider track and have to reinstall it after each build, perhaps it is loading with the active directory powershell module for some reason?
<#
.SYNOPSIS
Installs the AD PowerShell module from RSAT for Windows 10
.DESCRIPTION
Performs the following tasks:
- Downloads and installs Windows 10 RSAT for the appropriate system architecture
- Enables the RSAT AD PowerShell feature
- Updates help for the AD module
- Displays validation output
.NOTES
Requires an elevated PowerShell host.
Requires an internet connection to download the RSAT install.
The RSAT hotfix download (<100MB) will be stored in the Downloads
folder of the user running the script.
Checks the following before taking action:
- Is the system running Windows 10?
- Is the RSAT already installed?
- Is the AD PowerShell feature already enabled?
.PARAMETER Test
Switch parameter to validate the install. Performs the following:
- Displays the RSAT update file that was downloaded.
- Confirms the hotfix is installed.
- Displays help for Get-ADDomain.
- Run the cmdlets Get-ADDomain.
.EXAMPLE
Install-ADModule -Verbose
.EXAMPLE
Install-ADModule -Test -Verbose
#>
Function Install-ADModule {
[CmdletBinding()]
Param(
[switch]$Test = $false
)
If ((Get-CimInstance Win32_OperatingSystem).Caption -like "*Windows 10*") {
Write-Verbose 'This system is running Windows 10'
} Else {
Write-Warning 'This system is not running Windows 10'
break
}
If (Get-HotFix -Id KB2693643 -ErrorAction SilentlyContinue) {
Write-Verbose 'RSAT for Windows 10 is already installed'
} Else {
Write-Verbose 'Downloading RSAT for Windows 10'
If ((Get-CimInstance Win32_ComputerSystem).SystemType -like "x64*") {
$dl = 'WindowsTH-KB2693643-x64.msu'
} Else {
$dl = 'WindowsTH-KB2693643-x86.msu'
}
Write-Verbose "Hotfix file is $dl"
Write-Verbose "$(Get-Date)"
#Download file sample
#https://gallery.technet.microsoft.com/scriptcenter/files-from-websites-4a181ff3
$BaseURL = 'https://download.microsoft.com/download/1/D/8/1D8B5022-5477-4B9A-8104-6A71FF9D98AB/'
$URL = $BaseURL + $dl
$Destination = Join-Path -Path $HOME -ChildPath "Downloads\$dl"
$WebClient = New-Object System.Net.WebClient
$WebClient.DownloadFile($URL,$Destination)
$WebClient.Dispose()
Write-Verbose 'Installing RSAT for Windows 10'
Write-Verbose "$(Get-Date)"
# http://stackoverflow.com/questions/21112244/apply-service-packs-msu-file-update-using-powershell-scripts-on-local-server
wusa.exe $Destination /quiet /norestart /log:$home\Documents\RSAT.log
# wusa.exe returns immediately. Loop until install complete.
do {
Write-Host "." -NoNewline
Start-Sleep -Seconds 3
} until (Get-HotFix -Id KB2693643 -ErrorAction SilentlyContinue)
Write-Host "."
Write-Verbose "$(Get-Date)"
}
# The latest versions of the RSAT automatically enable all RSAT features
If ((Get-WindowsOptionalFeature -Online -FeatureName `
RSATClient-Roles-AD-Powershell -ErrorAction SilentlyContinue).State `
-eq 'Enabled') {
Write-Verbose 'RSAT AD PowerShell already enabled'
} Else {
Write-Verbose 'Enabling RSAT AD PowerShell'
Enable-WindowsOptionalFeature -Online -FeatureName RSATClient-Roles-AD-Powershell
}
Write-Verbose 'Downloading help for AD PowerShell'
Update-Help -Module ActiveDirectory -Verbose -Force
Write-Verbose 'ActiveDirectory PowerShell module install complete.'
# Verify
If ($Test) {
Write-Verbose 'Validating AD PowerShell install'
dir (Join-Path -Path $HOME -ChildPath Downloads\*msu)
Get-HotFix -Id KB2693643
Get-Help Get-ADDomain
Get-ADDomain
}
}
Get-Help Install-ADModule -Full
Install-ADModule -Verbose
#Install-ADModule -Test -Verbose
break
<#
# Remove
wusa.exe /uninstall /kb:2693643 /quiet /norestart /log:$home\RSAT.log
#>