Moving an Azure VM between networks

 

Moving an Azure VM between networks was before, delete, recreate, reattached disk as documented here:

http://blogs.msdn.com/b/walterm/archive/2013/05/29/moving-a-virtual-machine-from-one-virtual-network-to-another.aspx

Which works a charm by the way, however you can now powershell it as documented here:

https://fabriccontroller.net/blog/posts/migrating-your-microsoft-azure-virtual-machine-to-a-different-subnet-with-the-new-powershell-cmdlets/

“

$context = Get-AzureVM -ServiceName contosomed -Name server01

Set-AzureSubnet -SubnetNames "WFE" -VM $context

Update-AzureVM -ServiceName contosomed -Name server01 -VM $context.VM

“

Install MYOB on XenDesktop 7.5 in Azure on Server 2012 r2

 

Installing MYOB 19.10 in Azure Server Windows Server 2012 r2

Disable UAC via the registry, reboot

Install .NET 3.5

Just install the SERVER product for terminal services

Don’t just install it, do it via the old ‘add remove programs’

Install Application on Remote Desktop

Install

You may get stuck at this screen

If you do and hit cancel this is the error message

This is the workaround to this issue:

1. Log on to the system with Administrative Privileges
2. Open “Local Group Policy Editor” go to:
3. Computer Configuration
4. Administrative Templates
5. Windows Components
6. Remote Desktop Services
7. Remote Desktop Session Host
8. Application Compatibility
9. In the right pane, right click on ‘Turn off Windows Installer RDS Compatibility” and select Edit from the drop down menu
10. Select ‘Enable’
11. Hit OK

Hat tip for this http://community.myob.com/t5/Installing-and-upgrading/Upgrade-to-2014-2-hanging/td-p/263121

Rerun this install and it will work fine.

Few more next next nexts, Finish to complete

Then if you are using XenDesktop 7.5 allocate the application to users.

Good to go.

List to MYOB Supported platforms http://myob.com.au/business/customer-service-support/support/new-microsoft-environments-page/microsoft-windows-8-1257830102169

How to install and use Citrix WebInterface 5.4 on Windows Server 2012 R2

 

Prepare your Windows Server 2012 r2

Install the following roles and features:

• .NET Framework 3.5 Features
• .NET Framework 3.5 (includes 2.0 and 3.0)

• Web Server (IIS) with sub-components
• Management Tools with sub-components
• IIS 6 Management Compatibility
  IIS 6 Metabase Compatibility

Install Citrix WebInterface

• install Microsoft Visual J# from the XenApp 6.5 installation media
• Citrix WebInterface 5.4 from the XenApp installation media

After the installation is completed you can now open the Citrix WebInterface Management Console. At this point the installation will fail.

• You can work around this issue by creating a text file named mmc.exe.config in %WinDir%\SYSWOW64 with this content:

<?xml version ="1.0"?>
<configuration>
        <startup>
                <requiredRuntime version="v2.0.50727"/>
                <supportedRuntime version="v2.0.50727"/>
        </startup>
</configuration>

• Now in the Citrix WebInterface Management Console again and create the required sites

The file mmc.exe.config can cause issues with other tools, so remove it after you are done

• Now correct the CitrixWebInterface5.4.0AppPool in IIS

If you try to access a new WebInterface site you will receive an error message about .NET complilation.

You can fix this for all sites on this server by changing the .NET Framework version for the Citrix application pool:

1. Open Information Manager Service (IIS) Manager
2. Open your server
3. Open the Application Pools
4. Edit Basic (or advanced) Settings on CitrixWebInterface5.4.0AppPool
5. Chose .NET Framework Version v2.0.50727 (or Dot NET CRL 2.0 in advanced)

Thank you to Marcel Meurer, www.sepago.de/e/marcel/2012/09/25/how-to-install-and-use-citrix-webinterface-54-on-windows-server-2012 who I based this on.

PVS Target install silently

 

There are lots of issues with installing the target software via SCCM to build gold images. The command line needed is documented, but here is the right command line switch!

PVS_Device_x64.exe /s /v” /qn /norestart

The installation help file says nothing of this funny quote (“) but it is the secret source. Good luck.