Configure other network ranges on USG 3 & 4 gateway unifi

Configure other network ranges on USG 3 & 4 gateway unifi

Existing network (firmware latest as of 10/09/2016, controller ver. 5.29)

1. Make sure your NETWORK under Settings is setup how you wanted. For example, internal ip to
2. Forget old USG3 (have to do this or you cannot adopt a new USG; only one USG per controller)
3. Change computer IP to that of the default subnet in
4. Add new IP address via SSH.
a. Configure
b. Set interfaces ethernet eth0 address
i. NOTE: You set it to your desired IP address which you configured in step 1. Eth0 interface

is the first LAN1 port in the USG Pro 4
c. Commit
5. Adopt USGPro4 in Controller GUI
6. Change computer IP to the NEW IP subnet range, example
7. Double check the new USGPro4 has been adopted
8. I might have used the Controller GUI inform command, someone chime in if needed for other users
9. SSH into USGPro4
a. Configure
b. Delete interfaces Ethernet eth0 address
c. Commit -> Save – Exit -> Reboot
10. Wait for it to do it’s thang and boom, adopted and connected.


Install OEM branded Server 2016 to a VM

The cause of this issue  is that the Windows server does not recognize the ‘hardware’ as a HP Proliant server, licensing will not succeed because a Windows ROK license (Reseller Option Kit) is used.

There is a simple solution. A parameter can be added so that the virtual machines ‘think’ that they are running on real HP hardware. After creating the virtual machine:

  • Stop the virtual machine
  • Go to Edit Settings / Options / General and select “Configuration Parameters”



  • Add a row, paste “smbios.reflecthost” as the name, and true as the value

VMware issue


Change email adresses or reply adress office365 after removing last exchange server from on-premise

The operation on mailbox “User” failed because it’s out of the
current user’s write scope. The action ‘Set-Mailbox’, ‘EmailAddresses’, can’t
be performed on the object ‘User’ because the object is being
synchronized from your on-premises organization. This action should be
performed on the object in your on-premises organization.


To Fix this while running AD Sync, try the next thing.

There are several solutions to this, but the easiest and most ready-to-go is to modify the attribute “proxyAddresses” within Active Directory Users & Computers. Follow these simple steps:

  • Open up Active Directory Users and Computers
  • Click “View,” making sure “Advanced Features” is checked
  • Locate the user and pull up their properties
  • Go to the “Attribute Editor” tab
  • Click “Filter” and “Show only attributes that have values” (not required, but recommended)
  • Locate the attribute “proxyAddresses” and click “Edit”
  • Make adjustments to the addresses in the form of smtp: and SMTP:
    and ensure you just leave one primary email address
  • Click “OK” to save the editor changes and “OK” again to save the user. Exercise caution to only change this attribute, and that you get the syntax correct for each entry.

The changes will apply during the next scheduled sync. Alternatively, you can start it manually by running the command “Start-OnlineCoexistenceSync” from the DirSyncConfigShell.




But it might happen you dont have the tab Atibute Editor. In that case download ADExplorer.
Download Download AdExplorer (244 KB)
Run now from Sysinternals Live.

Connect after install to the local domain and navigate to the user.
Find: proxyAdresses and right click, select modify.

Add a string with capital for default/reply adress. lowercase will add a alias:


Remove hybrid configuration On-premise / Office365

When faced with this challenge, it became apparently that there wasn’t a great deal of information available around how to smoothly remove an hybrid configuration from an Exchange organisation, whilst MS walk through the process in the following technet blog entry the order in which MS suggest performing the steps required wasn’t actually possible and resulted in a number of errors.  I therefore wanted to provide some clarity around the process/ordering.  This process covers hybrid configurations in both Exchange 2010 and Exchange 2013.

Firstly I assume the following activities have already been completed;

  • All required mailboxes have been migrated off of the on-premise environment across to Office 365
  • If necessary all public folder content has been migrated across to Office 365, either to shared mailboxes or traditional public folders.
  • All Exchange related DNS entries (autodiscover,OWA etc) have been re-pointed to O365
  • All MX records for SMTP domains that are being managed by O365 have been re-pointed to O365

Once these activities have been completed we can start on the steps required to remove the hybrid config;

  1. Remove the organizational relationship from the on-premise environment as follows; ‘Remove-OrganizationalRelationship -identity “name_of_org_relationship”.  The identity of the organizational relationship can be obtained by using the ‘Get-OrganizationalRelationship’ if required.
  2. Remove the organizational relationship from the O365 tenant as follows; ‘Remove-OrganizationalRelationship -identity “name of_org_relationship”, Again the identity of the organizational relationship can be obtained by using the ‘Get-OrganizationalRelationship’ if required.
  3. Remove the federated domain(s) from the on-premise environment as follows; ‘Remove-FederatedDomain -domainname name_of_domain
  4. Remove the Email Address Policy/Policies associated with those SMTP domains that have been moved to O365.  This can simply be performed from on the on-premise Exchange admin console
  5. Remove the Accepted Domain entries from the on-premise Exchange admin console for those SMTP domains that have been moved to O365.  Again this can simply be performed from on the on-premise Exchange admin console.
  6. Remove the federation trust from the on-premise Exchange environment as follows; ‘Remove-FederationTrust -Identity “Microsoft Federation Gateway” By default the hybrid configuration wizard in Exchange 2010/2013 names the federation trust “Microsoft Federation Gateway”.
  7. Remove the remote domain associated with the Exchange hybrid configuration using the on-premise Exchange Admin Console.  This will be named something like “Hybrid Domain –”
  8. Remove the SMTP send connector from the on-premise environment as follows; ‘Remove-SendConnector “Connector_Name”‘
  9. Remove the inbound and outbound SMTP connectors that were created by the hybrid configuration wizard in the Exchange Online Protection Administration Console
  10. Finally remove the HybridConfiguration object from within Active Directory.  This isn’t supported in Exchange 2010 and its perfectly fine to leave the object in AD without any adverse effects.  If however Exchange 2013 is being used in the hybrid configuration, the following PS command can be used to remove the HybridConfiguration object;  Remove-HybridConfiguration


Once those steps are complete, all references to the previous hybrid configuration are removed leaving two separate and distinct Exchange environments, CompanyA on-premise and CompanyB in O365.