Quick one for troubleshooting domain communications with a local machine.
Checks the domain a machine is registered to:
nltest.exe /parentdomain
Tests Machine Health with Domain Controller:
nltest.exe /sc_query:fqdn.domain.name
Reset Machine Password:
nltest.exe /sc_reset:fqdn.domain.name
I needed to get a SCCM 2012 lab setup for my company. As this was a newer MS product I figured the install wouldn’t be that bad. Well it’s a pre-req / pre-configure nightmare.
Here is my loose and possibly incorrect way that I got a lab running.
Few notes about my deployment
Prep SQL Server box:
Prep CAS Box:
I had the above mentioned pre-reqs after going through the installer. I will list out the things I did to reslove these so you don’t have to go through the installer only to cancel out and reslove this requirements. (I wish Microsoft had done a better job at this installer. I thought they had learned, I thought wrong)
Failed Items:
Warning Items:
Installing Configuration Manager:
Microsoft just released SCCM 2012 to VL customers. Very excited to tear into it. However I got stuck right in the beginning of the installer with:
The WinRM settings are not configured correctly
Well looking at the logs here:
\Users\<user>\AppData\Local\Microsoft System Center 2012\Unified Installer\LOGS
I discovered:
[4/10/2012 9:20:08 AM] DEBUG – Server: localhost, winrm\client\auth\CredSSP = False
All you need to do to fix this is run the following commands on the computer you are running the installer from:
winrm set winrm/config/client/auth @{CredSSP="True"}
winrm set winrm/config/client @{TrustedHosts="*"}
Also run these commands on the computer you are installing too (if it’s the same box just run all commands)
winrm qc -q
winrm set winrm/config/service/auth @{CredSSP="True"}
winrm set winrm/config/winrs @{AllowRemoteShellAccess="True"}
winrm set winrm/config/winrs @{MaxMemoryPerShellMB="2048"}
That should take care of you. Just in case it doesn’t the old other thing I had done was to add .Net 3.5.1, all RSAT Tools, and IIS from Roles and Features.
Hope it helps. If it does please leave a comment below and let me know this was worth my time posting 😉
While I have to write a longer post about my overall feeling of Windows 8 and Metro I wanted to toss this one out there.
THANK YOU Microsoft for the Task Manager Performance Monitoring built it. Look how sexy and plan English my transfer rate is for copying a number of large files to my desktop (click for larger version):
Just fantastic, shows me the CPU is doing fine as it decompresses directly from network share and shows me that Network is in fact the bottleneck as the Disk I/O is not maxed.
If you are reading this its likely you googled for the answer to this very questions. “How do I install Exchange 2010 in a child domain?” Its almost like every step of the way you get another ambiguous error message.
Well if you know what to do its fairly easy.
1) Make sure you have an account that is NOT the administrator account that has Enterprise Admin, and Domain Admin of the ROOT domain.
2) Logon to a Windows 2008 x64 / or 2008 R2 x64 box that is a member of the ROOT domain. If you don’t have one just build one or temporarily move the new exchange server into the ROOT domain long enough to preform the following steps.
3) Logged in as your service account with Enterprise Admin and Domain Admin rights to the root open a command prompt (run as administrator if UAC is enabled).
4) Go to the directory you have the Exchange 2010 install located. I recommend using a direct Exchange 2010 SP1 install build.
5) Run the following command
ServerManagerCmd -i RSAT-ADDS
6) Reboot
7) Run the following command (Prep Legacy Permissions)
setup /pl
8) Run the following command (Prep Schema)
setup /ps
9) Run the following command (Prep Domain and Name Org)
setup /p /on:TestlaCorp
–Note: TestlaCorp is my test domain org name, please enter your desired org name.
9) Run the following command (Prep all Domains)
setup /preparealldomains
10) Follow these directions from the ROOT DC Domain Controller: (not totally sure this is required or not, skip and only do if you run into an issue)
11) Now go to your new exchange server box (rejoin it to the child domain if you had moved to the ROOT domain for the above commands).
10) Logon as that ROOT account with Enterprise Admin and Domain Admin for the ROOT domain. You will need to grant it local admin rights on the new child domain server you are planning on installing Exchange 2010 to ahead of logging in.
11) Run the setup as you normally would do. I usually follow this blog for those steps:
Final Notes: I noticed after installing that I was getting an error opening the EMC and it turns out it was just that the installer some how didn’t install any of the roles. Re-running the install fixed that.
Had a funny issue raised from the helpdesk today. All of a sudden all of our Wireless users were no longer to connect to the internal wifi network that was protected by 802.11x PEAP via Merkai -> RADIUS -> NPS (Network Policy Server) -> Active Directory.
We had errors like this:
“Network Policy Server discarded the request for a user.”
“An internal error occurred. Check the system event log for additional information.”
And of course the logs at c:\windows\system32\logfiles had nothing of value in them.
Another thing was that Event Logging from NPS stopped although the service was still running.
It turns out it was just because the certificate NPS uses was renewed automatically thanks to GPO / AD. NPS doesn’t handle the transition well.
All you have to do is change the certificate to another certificate and back to the one that was auto renewed. if you only have one then create another, change it to that, then swap back to the correct auto renewed on.
If you don’t know where to select it, it is under Policies -> Network Policies -> <your policy that grants users access) -> Constraints tab -> Authentication Mode -> Microsoft: Protected EAP (PEAP) [EDIT]
