Streaming Servers:

Open the MDOP server installation and choose App-V server then streaming servers

Click Next in the welcome screen as shown below

Accept the EULA and click next

Enter the user name and org name

Leave the default installation path default and click next

Leave the default for now and click next on the certificate page

Leave the default port selected and click next (Unless you have a reason to change it)

In the content path, please ensure to enter the UNC path for the content share (that maybe on file server, DFS or even one of the management/streaming servers)

Leave the default settings and click next

In the installation configuration please click Install

Once installed, please click finish.

By now you have all your infrastructure ready!

Here is few notes:

Go to this link and ensure you’re complying with the below

Best Practices for the Application Virtualization Sequencer

https://technet.microsoft.com/en-us/library/dd351420.aspx

· Follow the steps in this guide to sequence office 2010

https://support.microsoft.com/kb/983462

· Make sure to follow the following steps to make Office 2010 work

o Download the Office 2010 Deployment Kit and extract it to C:\app-v

o Run the kit by exactly executing this command: msiexec /i C:\app-v\offvirt.msi PROPLUS=1  (if you’re using the office professional edition)

· For troubleshooting:

o Make sure that the app-v service is started and you can telnet to the server by port 554 from the other servers and client zone

o Make sure that there are no packets being dropped between the client and server. To test that, please leave the client idle for 10 minutes, then run ping command to the app-v management server NLB name/IP and it succeed from the first packet.

o Make sure that the SQL service account is granted Logon As Service permission on both SQL servers, otherwise the failover/failback will fail

o Make sure that the App-v service account  is:

§ Granted Logon As Service permission on both management servers

§ Has read permission on the local NTFS permission of the content shares

§ Has read permission on the share permission of the content shares

§ In case of future publishing and using RTSPS, this account should has read permission on the certificate private key

§ Has administrative privilege on the SQL DB used for App-V

§ Make sure that this account has SPN registered in AD

· Install SCOM Agent on App-V Servers. Download and import the App-V management pack from this link https://www.microsoft.com/downloads/en/details.aspx?FamilyID=82b0397f-fac8-4c5a-b906-e87d0e57982a&displaylang=en

· Install SCOM Agent on SQL Servers. Make sure that the SQL management packs are already imported, otherwise it should be imported.

3.1.5 install Sequencer

to install the App-V Sequencer, please follow these steps on Windows XP or Windows 7 newly installed workstation.

In the checking prerequisites, please click next to install the missing components

Note: the above step may ask for a reboot.

Once the sequencer prerequisites are installed, the Sequencer installation will shortly began.

Please click next to start the installation

Accept the license agreement and click Next

On the destination folder page, please leave the default location selected and click Next then install

After installation completes, please click Finish

3.1.6 Client Installation

The client will be installed on client operating system (XP or 7)

Please run the app-v installation from the MDOP 2010 refresh splash.

It will prompt you for installation prerequisites, please click install and wait for the installation to finish.

In the client installation page, please click Next

Accept the license agreement and click Next

On the Microsoft update Opt In page, please choose to use Microsoft Update option and click next

Choose custom installation and click next

Leave the default installation directory and click next

Leave the default and make sure the drive is set to Q and click next

Leave the default maximum cache used and click next

Leave the default and click next

In the publishing server information, please ignore the data in the below snapshot and enter the below:

Display Name: App-V Management Servers

Type: Application Virtualization Server

Host Name: XYZ.domain.com

And leave the default port and click next

Click install and wait for the installation to finish

Click finish on the final screen

To be continued…

3 App-V Server Deployment

3.1 Pre-installation

3.1.1 Create AD groups

Create the following groups in AD

App-V Admins

App-V Users

3.1.2 Create content share

Create shared folder on the management servers and share them with the below permissions for NTFS and share permissions

App-V_admins: Full control

App-V_users: read only

Msappv: read only

Network Service: Read permission

3.1.3 install management server prerequisites

Install IIS 7 and make sure the below are selected

· ASP.NET (and all its required role services and features)

· Windows Authentication

· IIS Management Scripts and Tools

· IIS 6 Management Compatibility

Install and wait for the installation to complete and click close

Install .Net framework from features from add new feature wizard

3.1.4 install management server

open the application virtualization splash and choose to install management server role

Accept the license agreement and click next

Choose Use Microsoft updates when I check for updates and click next

Enter the registration information and click next

Choose the Typical installation to install Management Web Service, Management Console and Management services.

In the configuration database page, please scroll till you see the SQL cluster name created for this implementation and click next.

Choose to create a new database and click next

Click next in the certificate page

(Note: You can choose to use RTSPS only when you install the certificate. In this case, I’m only using RTSP)

Leave the default RTSP port selected and click next

In the administrators group page, please choose the previously created group (App-V Admins) and click next

In the app-v users page, please select the previously created group (App-V Users) and click next

In the content path page, please enter the content path

Be sure to select the network path where the content share will be. If you select by mistake another path, please follow the steps in the below KB to relocate to new location

https://support.microsoft.com/kb/930868

How to relocate the content directory for Microsoft app-v

Click finish. Restart your server.

Note:

When you try to connect to your server for the first time, you may get the below error

The resolution to that is to add the user you’re logging in with to the app-v admins group and it should open as below.

Follow the same steps to install the second management server, and be sure to select the same content path you provided in the first server deployment.

The final step is to go to the services console and change the app-v service logon name to the App-V service account if you want to use service account instead of Network Service. Once this service account is change, please follow the steps in this guide to create the required SPN

https://blogs.technet.com/b/appv/archive/2008/08/21/how-to-configure-the-app-v-management-server-service-to-run-as-a-service-account.aspx

To be continued..

Open the SQL server 2008 RTM installation and choose “New SQL Server Failover cluster installation”

When till the setup support tools are installed.

Choose enter the product key and make sure you have a valid key to continue the installation.

Accept the license agreement and click next

Click Next

- Make sure that all the prerequisites check passes successfully and click next

In the Feature Selection, please make sure to choose the following exactly as shown in the below screen.

Leave the default installation directory and click next

In the SQL network name, please make sure to enter a unique SQL cluster name and leave the default instance selected.

- In the disk space requirements page please click next after passing the checking

- In the cluster resource group, leave the default resource group name and click next

- Make sure to choose both logs and DB disks and click next

- Add the IP address and click Next

- Leave the default option and click next

Make sure to give the sql service account logon as service permission (it will be granted in installation, but make sure that it will won’t get overridden”

In the service account page, provide the appropriate credentials and click next

In the account provisioning page, leave it to Windows Authentication mode and specify SQL admins and click Data Directories tab

In the data directories tab, please make sure specify the Logs directory in the N drive and the DB in the O drive. (In this example it’s N and O, you can configure the drive as you like)

Choose the below checkboxes and click next

Wait for the rules to run and click next

In the installation page, please review the settings and click install

Verify the installation completion and click finish.

Close the installation on the first node. Logon to the second node and run the installation splash. But choose to add node to a cluster option.

Specify the product key

Accept the license agreement

Wait for the support files to get installed and click next

- Click next after passing the prerequisites checks

- Choose the correct SQL instance name and click next

- Make sure to provide the same credentials for the service account. Same conditions apply.

Chose to send Windows and SQL error reports to Microsoft and click next

- Wait for the Add Node Rules page to finish and click next

- On the final page, review the settings and click install

- Verify that the SQL installation went successfully and click close

Make sure to take a full system state and cluster backup after each successful deployment. By this step, you’re ready to install App-V server components.

To be continued..

This document intended to provide guidance on how to install and configure App-V 4.6 infrastructure. In this guide, you’ll be able to follow a step by step guidance that will walk you through Application Virtualization server deployment. This guide includes all the steps, starting from SQL deployment till application sequencing.

2 Preparing SQL Database Cluster

2.1 Pre-installation configuration

Before configuring any server or install the services on SQL Server, please follow the steps below

- Open TCP/IP settings for the heartbeat interface and make sure that the register this connections’ addresses in DNS is not checked.

- Disable NETBIOS over TCP/IP

In the network ordering, please make sure that the Public interface is set before the heartbeat as shown below. And disable IPv6

2.1.2 Windows Cluster Configuration

In able to install SQL cluster, we need to install and configure windows clustering services first. Please follow the below steps to install Windows Server 2008 Failover cluster services.

- Open Add Features wizard and select failover cluster

- Choose failover cluster and click next then finish

2.1.3 Create a new Windows cluster

First, present the LUNs to the SQL servers and make sure that the persistent reservation is enabled by choosing Windows Server 2008 (or Windows LH) from the cluster administrator page.

- Open the failover cluster console from administrative tools, and choose to create a new cluster

- Browse for the server names of your cluster nodes

Write the cluster name and IP addresses. Cluster name must be unique, and the IP should be available and in the same network where the IP addresses of the nodes. Be sure that you have permission to create computer objects in the domain before this step.

Click Next

click finish on the confirmation page

open the failover cluster and make sure that all resources are up

Make sure to add the shared disks to be clustered resources by right click on the storage and choose Add Disks.

Before installing SQL, make sure to install .NET framework and Windows updates. It’s also recommended to add MDTC as cluster resource, but SQL service shouldn’t depend on the DTC service. Below are the steps to add DTC services in the cluster console. To do so, please follow the below steps:

- Right click the services and choose configure a service or application

- Choose the DTC service as shown below

- Choose a unique IP address and leave the default name

- Choose the storage to assign the DTC service to.

- Click next

Click finish on the confirmation page.

The next step is to install SQL cluster. Check the next part for the step by step

To be continued…

I always use Windows Server 2008 R2 for my laptop, and I just installed DirectAccess and couple of updates. After that, I couldn’t connect to virtual machines itself and it gets me the following error

Cannot find the physical computer that runs the virtual machine. Try to flush your DNS cache (run ipconfig /flushdns). Then try to connect again. If the problem persists, contact the administrator of the physical computer or your network administrator

Thanks to Thomas, I found the solution for that problem. Simply do the following two steps

go into the Registry and delete "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\DnsPolicyConfig"
in an elevated command prompt, enter: sc control dnscache paramchange

"NLB Stopped - Configuration Failure" error message may occur when you try to enable the NLB feature in Forefront TMG 2010 if the network adapters are VLAN tagged or teamed

The Forefront TMG firewall service leaks memory when you access a site of the "HTTPS Inspection exception" list in Forefront TMG 2010

The L2TP VPN connection may randomly disconnect when you change or apply an access rule on a VPN server that is running Forefront TMG 2010

"0xC0040410" error occurs when you try to join an array member to an array in Forefront TMG 2010 SP1 if the array is managed by Forefront TMG 2010 EMS

A 502 proxy error occurs when you try to create an HTTPS connection if a downstream proxy has Forefront TMG 2010 installed

A replica installation of Forefront TMG 2010 EMS fails and a "0x80070002" error is logged

Forefront TMG 2010 Firewall Service-based member of a Forefront TMG array stops responding when another Forefront TMG Firewall Service-based member is stopped

0x80131500" error occurs and the IsaManagedCtrl service does not start in Forefront TMG 2010 after you install Exchange 2010 SP1 if the Email Protection feature is enabled

To request the update, please visit the below link

https://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2433623&kbln=en-us

I found the below way to install the slipstreamed source of TMG with SP1 in one DVD. Follow the steps as shown below to end up with the upgraded copy

1. Run the following from an elevated command prompt:

ServerManagerCmd.exe -inputpath ^<DVD_path^>\FPC\PreRequisiteInstallerFiles\WinRolesInstallSA_Win7.xml -logPath C:\Windows\TEMP\TMG-Prerequisites.log

1. Prepare a Forefront TMG SP1 slipstream DVD with the following steps:
   1. Copy the Forefront TMG DVD and the Forefront TMG SP1 MSP file to a local drive on the target computer. For the purposes of this example, let’s assume this is c:\temp\TMG.
   2. At a command prompt, type the following command and press ENTER.
      msiexec /a c:\temp\TMG\FPC\MS_FPC_SERVER.msi /p TMG-KB981324-amd64-ENU.msp /qb /L*v c:\tmg\log.txt
      When the operation completes, you will have a full installation of Forefront TMG already upgraded to Service Pack 1.

Enjoy.

Hello there,

I’ve been (and I think most of you did) through the WSUS configuration and waiting for days for the download to finish.

That’s because the the BITS technologies that limits that foreground download, and enable the background downloads – to least impact the bandwidth.

We used to use this command in WSUS 2.0

WsusDebugTool.exe /tool:setforegrounddownload

But in WSUS 3.0 it’s not applicable, and if you tried to execute it, it will get you with the below error

Running... SetForegroundDownload

Error processing node: SetForegroundDownload

System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)

   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)

   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)

   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)

   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)

   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)

  at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

   at System.Data.SqlClient.SqlConnection.Open()

   at Microsoft.SoftwareDistribution.Tools.SqlHandler.HandleQuery(TextWriter dataWriter, String baseDirectory, ArrayList sqlQueryList)

   at Microsoft.SoftwareDistribution.Tools.SqlHandler.DumpData(String baseDirectory, String nodeName, XmlNode infoXml)

   at Microsoft.SoftwareDistribution.Tools.SusServerTool.ProcessDumpNode(XmlNode dumpNode)

In WSUS 3.0, in able to speed up the downloads (foreground mode), you need to run this command

"%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S %Computername%\MICROSOFT##SSEE -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

To revert it back to normal, you can run the same command again and change the value to 0

"%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S %Computername%\MICROSOFT##SSEE -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=0"

Once you done that, you need to reset the update services service.

Whenever you mess up with authentication methods on the IIS or through powershell, services may not function properly, especially the published ones. Blew is the default authentication methods published at Exchange Team Blog site:

Exchange Server 2010 with the Client Access Server (standalone):

Location	Authentication	SSL Setting	Management
Default Web Site	Anonymous	Required	IIS Management Console
aspnet_client	Anonymous	Required	IIS Management Console
Autodiscover	Anonymous / Basic / Windows Authentication	Required	Exchange Management Shell
ECP	Anonymous / Basic	Required	Exchange Management Console or Shell
EWS	Anonymous / Windows Authentication	Required	Exchange Management Shell
Microsoft-Server-ActiveSync	Basic	Required	Exchange Management Console or Shell
OWA	Basic	Required	Exchange Management Console or Shell
Powershell	Anonymous	Not Required	Exchange Management Shell
RPC	Basic / Windows Authentication	Required	Exchange Management Shell
RpcWithCert	all options Disabled	Required (128 bit not checked)	N/A
OAB	Windows Authentication	Not Required	Exchange Management Console or Shell

Exchange Server 2010 Mailbox role (standalone):

Location	Authentication	SSL Setting	Management
Default Web Site	Anonymous	Required	IIS Management Console
PowerShell	Anonymous	Not Required	Exchange Management Shell

CMDlet list for those that can only be modified in the Management Shell:

Set-AutoDiscoverVirtualDirectory

Set-WebServicesVirtualDirectory

Set-PowershellVirtualDirectory

Set-OutlookAnywhere (for the RPC virtual directory)