Last Executed: This script has not yet been executed.

Recently had a problem with a Powershell script that was configured via Group to deploy at start up.

The problem I had was that no matter what the script would never run. Doing a GPResult /z it would show me the script is being applied but with the following message:

Last Executed: This script has not yet been executed.

After much searching and testing I found that the script would run if I removed the spaces in the script name.

I know its a simple mistake but the server did not tell me that it could not find the file.



Configure your windows pc as a Wireless Access Point

I found the interesting post on how to configure your computer to serve as a wireless access point.


1. Open command prompt as administrator
2. netsh wlan show drivers Look for Wifi driver – find ‘Hosted network supported’ – if Yes, then OK
3. netsh wlan set hostednetwork mode=allow ssid=your_chosen_ssidkey=8_or_more_character_key
4. netsh wlan start hostednetwork
5. Go to network and sharing center –> Change adapter settings. Right click your internet connected adapter and go to properties. Click the sharing tab. Check the ‘allow other network users to connect through this computer’s internet connection.

Create a shortcut to the command in step 4 preceeded by ‘cmd.exe /c ‘ and stick on the desktop or wherever to make it easier to start the hotspot after rebooting. Remember to change the shortcut properties (advanced) to run as administrator. To stop the hotspot, replace start in step 4 with stop.

Exchange SMTP connectors

Exchange 2007/2010 to 2010 migration  =  Don’t need to create new SMTP connector in Exchange 2010 – Just add Exchange 2010 as source server and after migration remove old server as source.


Exchange 2003 to 2010 migration = Need to create new SMTP connector on Exchange 2010 server.


You will receive the below error when you try to the add the new Exchange 2010 server to the SMTP connector that already exists in Exchange 2003 (In Exchange 2010 EMC). Exchange 2010 doesn’t recognize the 2003 SMTP connector so a new connector has to be created.

Enable Powershell remoting and connect

I’ve had to search around a bit to find all the commands to enable remotely connecting to Server 2012 using powershell.

#To enable remote connections on the server:


#To connect remotely from your workstation

Enter-PSSession -computername Server_Name -Credential administrator

Remember you have to use the server name and not the IP address otherwise it will deny you access.




Hyper-V Manager missing Server 2012

So you’ve installed the Hyper-V module in Server 2012 and are ready to start setting up your virtual environment but for some reason you cannot access the Hyper-V manager.

The reason is you need to add the Hyper-V management tools as a feature.

Go to add features in Server manager and the tick the box below:

Running SBS2003 to SBS2011 migration

  1. Do the following Pre-Checks to make sure you won’t have problems during the migration:


  • Make sure you are running a Class C subnet ( – Migration is not supported on other subnets.
  • It is recommended that you only have one NIC active during the migration – No external NIC active (I have done successful migrations with the External NIC active though).
  • Uninstall ISA before you do the migration. This could prevent certain issues that might arise. We had problems with ISA every time we ran the migration with it still on. ISA will definitely cause problems with the mailbox moves (Even if you try the MS workarounds).
  • Ensure event viewer clean – Especially replication and DNS issues.
  • Make sure you don’t have a single label domain name (The domain name has to have a suffix Eg. test.local).


  1. Install pre-requisites


  • Powershell 2.0
  • MS baseline config analyser


  1. Make a backup of system state. You will be able to start over again from this backup should things go wrong.
  2. Run migration preparation tool (From SBS2011 disk) – This will raise functional level and run the necessary steps to prepare the source server for migration.
  3. When done it will scan the source server for problems – Resolve these problems before you continue.
  4. Create the answer file.
  5. Make sure the answer file is on a disk (Flash drive or hard drive) that is connected to the new SBS2011 server (Destinations server) and run the migration from the SBS2011 disk.
  6. Run through all the steps (The migration process can take a couple of hours to complete).
  7. Log in with an admin account but not the built in administrator account (You can’t run the migration step with the built in administrator account).
  8. Run the migration steps (This includes moving the mailboxes, installing the certificate etc.)
  9. Move all data and re-create shares.
  10. Install 3rd party apps.
  11. Configure backups.
  12. Decommission the old server.