I have been involved in a small migration project over the last couple of months and will be sharing my notes. In all fairness most of this comes from Microsoft guides which are pretty good and comprehensive. What I’ll be sharing is a rather condensed version so you might want to read through the original articles before undertaking your own migrations.
First up is the network policy server migration which is very straight forward.
NPS Migration Steps
Preparing the source server:
- Gather information for the table above.
Preparing the destination server:
- Configure new server OU and group membership identical to the source.
- Install NPS role service.
Exporting settings from the source server (Windows Server 2008)
- On the source server open elevated command prompt and run:
netsh nps export filename=”\\share\IT\NPS\file.xml” exportPSK=YES
Importing settings to the destination server:
- On the destination server open elevated command prompt and run:
netsh nps import filename=”\\share\IT\NPS \file.xml”
Verifying the NPS migration
- Check that NSP is running on the destination server:
- In elevated command prompt run: sc query ias
- In the command output, verify that RUNNING is displayed next to STATE.
- Verify NPS config has been migrated:
- netsh nps show config
- Verify that the destination server is not using default NPS settings. For example, default settings display a single policy under Connection request policy configuration with the name Use Windows authentication for all users.
- Verify that NPS console is displaying correct settings
- Using the NPS console navigate to Policies, RADIUS clients and servers…etc to make sure settings are displayed as expected.
- Verify Authentication methods:
In this case NSP02 uses certificate based EAP methods, the destination server might already be provisioned with a suitable certificate through autoenrollment. You might also be required to manually enroll the destination server with a computer certificate.
- To view the certificates associated with EAP methods on CAE-WT-DC02, open the NPS console.
- Open Policies → Network Policies → Wireless Users Services/Wireless Users General.
- Check the Constraints tab.
- Click Authentication Methods, and then under EAP Types click Microsoft: Protected EAP (PEAP).
- Click Edit, verify that the correct certificate is chosen next to Certificate issued or Certificate issued to, and then click OK.
- Verify client connections:
- On the destination servers In the event viewer console tree, open Custom Views\Server Roles\Network Policy and Access Services.
- In the details pane, verify under Event ID that event number 6272 is displayed.
- Events 6273 or 6274 indicate that client authentication attempts are unsuccessful.
- If no events are displayed, client connection requests are unable to reach the destination server, or the server is not logging authentication attempts.
Migration file store – you can of course export the file locally on the source server and then manually copy over.
DNS and IP addresses – Depending on how your radius clients connect to the NPS server for authentication you might want to assing the same IP addresses to the new servers, update your DNS records accordingly or update each radius client separately.
After not a lot of action on the IT front (mainly due to being on maternity leave for the last two months) I’ve signed up for the Microsoft insider program to check out for myself what the hype is all about.
Microsoft don’t recommend installing the technical preview on your primary computer as it is still very much a work in progress and potentially unreliable. There were a couple of reasons why I decided to go against the advice – firstly my laptop wasn’t running that well and I would have ended up rebuilding it pretty soon anyway but more importantly if I was to do the sensible thing and install Windows 10 on a virtual machine I would never get the motivation to actually use it.
In all honesty it doesn’t feel that different compared to Windows 8. There is a start menu which I quite like and you can customize the live tiles pretty well too. I haven’t quite got to grips with the task view yet but it might be useful for some users. My favourite feature so far is being able to use keyboard short-cuts like Ctrl+V and Ctrl+F inside command prompt. Oh and I nearly forgot to mention it is now possible to turn off/restart the pc from the start menu. On a more serious note it looks like Microsoft are really interested in getting some feedback – what they will do with the information is yet to be seen but ever the optimist I have already submitted a few suggestions via the Windows Feedback app.
Windows 10 will definitely please people that were after a more Windows 7 feel but it is not as ground breaking as Microsoft would want everyone to believe unless I am missing something and that’s what the comments are for.
To sign up for the tech preview go to: http://windows.microsoft.com/en-gb/windows/preview.
It turns out that Cisco AnyConnect VPN (through an ASA) doesn’t support NTLMv2. In server 2003 the Default Domain Controller Policy was set to Sent NTLM response only. This has changed from Server 2008 and higher which by default enforces NTLMv2 so if you want to carry on using NTLM authentication with Cisco ASA you will need to modify the Default Domain Controller Policy.
The failures you will see on the ASA and in the DC security log aren’t overly descriptive or helpful:
ERROR: Authentication Rejected: AAA failure
Reason: Unknown user name or bad password
User Name: username
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
The group policy setting you want to modify is: Default Domain Controller Policy\Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level
Value: Send NTLMv2 response only. Refuse LM
Description: Client computers use NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controllers refuse to accept LM authentication, and they will accept only NTLM and NTLMv2 authentication.
There are security implications with doing this but it all depends on your environment. You can find more details here: http://technet.microsoft.com/en-us/library/jj852207(v=ws.10).aspx
Just a quick post today. If one of your Office365 users suddently can’t login to Outlook 2010 (most often after password change) and you’re absolutely sure the password you’re using is correct, i.e. you can sign into outlook.office365.com and lync give this update a go: http://www.microsoft.com/en-us/download/confirmation.aspx?id=29361 . It’s worked a treat for me today!
I think I may have finally found a solution to my problems with IPsec VPN on Windows8. When I first installed Windows8 the Cisco IPsec VPN client worked fine for some time – I’m not exactly sure how but it did. Unfortunately after a few weeks while I could still connect to the VPN I couldn’t actually access anything across the tunnel. RDP, ping…nothing would get through.
I resorted to using Shrew Soft VPN client for a while which mostly worked but I found with some VPNs it just wouldn’t connect and I would have to use a Windows7 VM to connect to those. Today I have decided to revisit the whole situation and came accross this post .
I didn’t have the Cisco VPN client installed at that point so went straight onto installing Citrix DNE. But if you already have the client you might want to install it first.
1. Download and install Citrix DNE.
2. Install Cisco IPsec client.
That’s all you should need to do but I’ll report back after a few weeks just in case it mysteriously breaks again. In the meantime if anyone has a better solution I’d be really glad for it.
I’ve recently spent a considerable amount of time trying to figure out why a client’s transaction logs were growing at the rate they were. I am talking 50GB worth of logs for one store every day. There really wasn’t anything warranting such growth. The usual things that came to mind like inbound/outbound spam issue didn’t apply. I have done a message tracking search to confirm this and with hindsight I should have really spotted the issue at that very point.
I have limited my search to a specific time period – but I would get a few messages showing sent date outside of the range. This was because the range you set in message tracking is when the message was logged – not when it originated. For some reason I decided not to pay any attention to this and persevere with some transaction logs analysis.
Scott Oseychik’s guide on transaction log analysis is great for this:
- Download the “Unix for Win32” utilities fromhttp://downloads.sourceforge.net/unxutils/UnxUtils.zip?modtime=1172730504&big_mirror=0
- Extract all files from the UnxUtils\usr\local\wbin subsirectory to C:\UNIX
- Download strings.exe fromhttp://www.microsoft.com/technet/sysinternals/Miscellaneous/Strings.mspx, and place strings.exe into C:\UNIX
- Make a C:\TMP directory (Unix tools need a Win32 equivalent of /tmp)
- Make a directory for all your transaction log files (i.e. D:\customers\test), and place all the logs in this dir
- From a cmd prompt, navigate to your C:\UNIX dir
- Run the following command:
strings -q -n 16 D:\customers\test\*.log | cut -f3 -d: | sort | uniq -c | sort | tee c:\log-output.wri
If you open the wri file (just use a text editor of your choice) you get a list of 16 character strings sorted from the least number of occurrences to the largest. While this won’t tell you exactly what the problem is it will definitely point you in the right direction.
In my case I had a totally ridiculous number of “Out of Office Reply” – so much so the next highest expression wasn’t anywhere near it. At this point it finally occurred to me that the messages “randomly” showing in message tracking were the culprit. While they may have been sent a while ago they were still looping on the Exchange server and constantly generating new transaction logs and coming up in each message tracking search.
Now I just had to stop these messages by disabling the automatic reply on each offending mailbox. As usual in hindsight it sounds very simple.
If the RSA server time is out by more than 3 minutes you will find some users completely failing to authenticate and some being prompted for the next token code. Once you correct the server time it is good to resynchronize all the tokens. I have run this batch job on a windows server but I’ll include instructions for UNIX based and appliance as well.
1. From command prompt run:
C:\Program Files\RSA Security\RSA Authentication Manager\utils>rsautil sync-tokens -I
2. You’ll be prompted for a a few bits of information including the path for the output file. The whole process should look like this:
Authenticator Bulk Synchronization Utility am-7.1.0-build20080715085805
Copyright (C) 2008 RSA Security Inc. All rights reserved.
Enter the absolute path for the output report file : c:\sync.txt
Enter the base security domain name for recursive search [(none)]: none
Enter the type of token selection [ (all) | file ]: all
Choose a token filter [ assigned | unassigned | (both) ]: both
What action do you wish to perform? [ (list) | modify ]: modify
Enter type of clock offset value [ absolute | relative | (none)]: absolute
Enter clock offset value : 0
Do you want to reset the Next Tokencode Mode? [ y/n ]: y
Do you want to reset the last login date and time? [ y/n ]: n
Do you want to clear user lockout information? [ y/n ]: y
Enter administrator user ID : admin
Enter administrative password : ***********
Authenticator Bulk Synchronization Utility am-7.1.0-build20080715085805
Copyright (C) 2008 RSA Security Inc. All rights reserved.
Started job on Wed Aug 20 10:19:51 EDT 2008 with ID = ims.e07c584ba263650a018d923bd0ac085d
3. That’s all you need to do. You can check the output file to get a list of tokens that were modified and their current status.
RSA Authentication Manager 7.1 – Applicance and UNIX based
I haven’t tried this so don’t take my word for it but it is the procedure from RSA support so hopefully not completely useless.
1. Connect to the Appliance using the console or an SSH client. (For remote access using an SSH client, verify in the RSA Operations Console that the Appliance is enabled for SSH connectivity.)
2. Log on using the emcsrv account and the Operating System password.
3. Switch users to root. Run: sudo su
4.When prompted, enter the Operating System password.
5. Switch users to rsaadmin. Run:su rsaadmin
6. Set the current directory to the folder that contains the RSA utilities.
Run: cd /usr/local/RSASecurity/RSAAuthenticationManager/utils
7. Set the environmental variables. Run: . ./rsaenv (This command begins with a period, space, period, and forward slash)
8. Set the correct time on the RSA Authentication Manager server.
9. Synchronize the tokens:
10. (Recommended) Create a text file where you can write output from the command. On the Appliance, a convenient location is /tmp/sync.txt.
11. Run: ./ rsautil sync-tokens -I (Run this command as rsaadmin.)