Rookie Mistake: Don’t Forget to Register NPS Server in AD

Rookie Mistake: Don’t Forget to Register NPS Server in AD

I have been playing around with NPS for a while but today was the first time I had ever set up an Network Policy Service Server on a Member Server in a domain. I then wanted to use it as the Primary Server for Authentication for one of our RADIUS clients but couldn’t figure out why I wasn’t getting Authenticated, I had set it up exactly the same as my other NPS Servers. Checking the Event Viewer I noticed that I was receiving the Event ID 4402 reporting that “There is no domain controller available for domain %1”. A lot of posts out on the Internet were leading me in the direction of DNS issues or Firewall issues but none of these were the issue. I then found this post by Geoff @ UVM and it became very clear what I had forgot to do! I forgot to Register the NPS Server in Active Directory. As soon as I had done that, everything started working as expected!

To Register the NPS Server in Active Directory:

  1. Open the NPS management console
  2. Right-click on NPS (Local)
  3. Click on Register server in Active Directory

I won’t forget that one again!

Until next time!

PowerShell Script: Delete Files Older Than 7 Days

PowerShell Script: Delete Files Older Than 7 Days

Another file operations PowerShell script that was recently required. This time we had a folder that contains a large number of log files that were never rotated and took up a large amount of disk space. These logs are only used for troubleshooting issues if they occur and it is rarely required for us to go over log files older than 7 days, so why are we keeping the rest?

Here is an easy one liner to help!

Until next time!

Get-ChildItem –Path “E:\TEMP\Logs” –Recurse | Where-Object{$_.LastWriteTime –lt (Get-Date).AddDays(-7)} | Remove-Item
Move Root Certificate Authority from Windows Server 2003 to Windows Server 2008

Move Root Certificate Authority from Windows Server 2003 to Windows Server 2008

Just recently I moved our Root Certificate Authority from what was originally an Small Business Server 2003. A while back I did run the Transition Pack, to upgrade it from an SBS server to a full Windows Server, but we had left it running Active Directory and it was still our Certificate Authority.

We decided that it was time to finally shut down this old server, but before we could, we had to move these essential services to another server. Searching around for what others had done I stumbled across this blog and it became the foundation of my technical solution.

At the end of the day, the migration went through successfully and I have the link below to thank for it!

Move Root Certificate Authority from Windows Server 2003 to Windows Server 2008

Thanks Scott for the great and helpful post!

Using Server 2008 R2 for File Server

Using Server 2008 R2 for File Server

Well lately I have been working on moving a lot of network resources from our old (ex-Small Business Sever) server to new server hardware which is now running the Windows Server 2008 R2 operating system. It has been a slow process of moving services and applications around, but just recently I finally removed our old server from the DFS replication and namespace. We are now purely running on the Server 2008 R2 for file serving in our office and it has introduced a lovely feature that should have been there from the start:

If a user does not have access to a folder or file, that folder or file is no longer visible to them.

That is perfect! Obviously a small thing but a very nice thing!