The string is missing the terminator: “. Azure child Runbook

As highlighted by this page: Here it seems that errors from Child Runbooks in Azure is not really displayed correctly.

In my case above is the error message I was getting. The problem in the end was that my script was referencing a registry key that pointed to HKCU which I assume doesn’t exist at the time.

The workaround is to add the child runbook in small sections to troubleshoot the error message.

Server 2008R2 – Secondary IP Address registering in DNS

I recently had a requirement to run 2 IP addresses on the same nic on a server 2008R2. The problem was that only 1 IP address was routable over the MPLS and the second IP address kept registering itself in DNS.

To resolve the issue I found the following command:

Netsh int ipv4 add address “Local Area Connection” <IP Address> <Netmask> skipassource=true

Just remember to not add the secondary IP address via Network and Sharing center.




What do you need when you want to deploy Lync in your environment

– 3x Server 2012 R2 servers (Can be virtual machines)

1. Access Edge Server

2. Front End Server

3. Office Web App Server

– 4x Public IP’s

– Unified communication public certificate (4 names)

The Office Web App server is required to properly share PowerPoint presentation.

For PABX integration you would require another server that will be the mediation server. You would also need a SIP device (Usually provided by PABX company but has to be Lync capable)

Migrate to Office 365 and use Migrationwiz to migrate mailbox data

  1. Get Office 365 admin login details (Will be emailed to you when you buy Office 365 online or from 3rd party supplier that will purchase Office 365 on your behalf)
  2. Login and ensure that the required amount of licenses is active – Get these activated well in advance
  3. Add email domain
    • You would need to create a TXT record for the domain to verify that you own the domain. Only once this is done can you add the domain on Office 365 (Make sure you do this well in advance)
  4. Get a populated user list with the following information for Office 365 user creation (Template can be downloaded from Office 365 portal)
    • User Name (Email address)
    • First Name
    • Last Name
    • Display Name
  5. Import user list to Office 365 (Create bulk users)
  6. Get a populated user list for user creation in Migrationwiz and required credentials for migration
    • Source Email
    • Source Login Name (For Exchange you can setup an account with impersonation and delegation rights and then specify this account for all the login names)
    • Source Password (For Exchange you can setup an account with impersonation and delegation rights and then specify this account for all the passwords – Don’t need to get individual passwords)
    • Destination Email (Will only be different from source if moving to new email domain)
    • Destination Login Name (Use the admin account for Office 365)
    • Destination Password (Use the admin account for Office 365)
  7. Get OWA address for source server (If using Exchange)
  8. Create migrationwiz project and specify source and destination details
  9. Import user list to Migrationwiz
  10. Download and install the sign in assistance and the windows azure PowerShell module for Office 365
  11. Open Azure PowerShell and run the following commands (This give the specified account full rights to all the mailboxes on Office 365 which is required for migrationwiz. Should only be done after all Office 365 users have been created):

$cred = Get-Credential

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $cred -Authentication Basic -AllowRedirection

Import-PSSession $session

Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User ‘YouOffice365AdminUser’

  1. Create admin account for migrationwiz on source server and assign impersonation or delegation rights to account (Exchange only)
    • Preferably use impersonation as this will use the users actual account and you won’t be limited on the amount of concurrent connections to Office 365
    • If using delegation it will use the admin account for the migrations and account will be limited on the number of concurrent connections to Office 365 (E.g. Limited to 4 or 5 migration that can run at a time)
    • This account needs to be specified as the Source login name and password for the document that you will import to migrationwiz
    • It is recommended to set up both Impersonation and delegation so that you can fall back on the other if one fails
    • Run the following command to setup impersonation:

New-ManagementRoleAssignment -Role ApplicationImpersonation -User ‘useraccount’

    • Run the following commang to setup delegation:

Get-mailbox | add-MailboxPermission -user ‘useraccount‘ -AccessRights fullaccess -InheritanceType all 

  1. Run migration of mails only (No calendar, tasks, notes or contacts as this changes on a daily basis – It will create duplicates if users make changes to items that has been migrated and we run migration again)
    • Migrate only mails that are older than a month (Newer mails will only be migrated with switchover – If you migrate all mails and user make change it will also create duplicates)
    • This needs to be done well in advance as this might take a while to complete depending on size of mailboxes and line speed
    • This will cause a lot of traffic on the line so communicate this to the client
  2. 1-2 days before switchover run migration for mails later than two weeks
  3. Change MX and autodiscover record to Office 365
  4. Run migration wiz for all mails and this time include all items (Calendar, contacts, notes and tasks)
  5. Two days after switchover run migration wiz again (MX records will take time to propagate so some mails might have been sent to old mail server)

VMware ESXi 5.5 – Error: ramdisk ‘tmp’ is full

Received below error as there was not enough free space on current (Default) scratch area space (Area to wright temp file to – required for host updates)

ESX error

  1. Need to change scratch location to area that have sufficient free space
  2. Create a new folder on datastore for each host using the following naming convention: ‘.locker-hostname
  3. Put host in maintenance mode
  4. Change scratch area for hosts to new folder location (Configuration > Advanced settings > ScratchConfig)
    1.  You would have to use the location name for the datastore (E.g. ‘/vmfs/volumes/5267c981-9a88a078-f998-90b11c592c9a/.locker-hostname’)
  5. Reboot host
  6. Exit maintenance mode


Error when trying to promote DC – Failed to configure the service NETLOGON as requested “The wait operation timed out”


The following resolution steps can be taken should you receive this error.

  • Changed DNS on local network adaptor – Enter IP of another DNS server (Don’t put local IP as DNS).
  • Check entries in DNS server and remove A records of server you are trying to promote (Might have legacy records if it was a DC before).
  • Run dcpromo while Netlogon service is stopped
  • Import registry setting from working DC for netlogon
  • Rename netlogon files and restart netlogon service
  • Ensure time is correct – Compare to working DC’s
  • Stopped any services that might be using the Netlogon service
  • Uninstall DNS from the server you are trying to promote

Important things to note on Exchange 2013

  • Can’t migrate from Exchange 2003 directly to Exchange 2013.
  • You need SP3 installed for Exchange 2010 and latest roll up update for Exchange 2007 when migrating to Exchange 2013.
  • Can run on Server 2008 R2
    • Need more pre-requisites installed compared to Server 2012
  • No longer 5 roles – Broken down to Client access and Mailbox role.
    • Unified messaging included in mailbox role.
    • Currently no Edge server but Exchange 2010 Edge server can be used with Exchange 2013.
  • Only 50 databases can be mounted on a mailbox server – Exchange 2010 could mount up to 100.
  • Public folders are no longer replicated in multi-site environment. It will be located in one location.
  • Exchange 2013 is much less resource intensive with regards to IOPS on disks, so cheaper disks can be used for your Exchange server. There is approximately a 99% IOPS reduction compared to Exchange 2003.
  • Web App now can now be used offline.
  • Built-in anti-malware (Previously only anti-spam).
  • Automatic failover to DR site.