Working with Powershell locked down? Unlock it…

 

If the machine you are running on and locked down there are several options to running the scripts shown below.

Via PowerShell - Get-Content AScript.ps1 | Invoke-Expression

Via DOS (note the spurious characters coming from the piped file) – TYPE AScript.ps1 | PowerShell.exe -noprofile

Or via a script to disable the execution policy by removing the AuthorizationManager in the current PowerShell session:

function Disable-ExecutionPolicy {($ctx = $executioncontext.gettype().getfield("_context","nonpublic,instance").getvalue( $executioncontext)).gettype().getfield("_authorizationManager","nonpublic,instance").setvalue($ctx, (new-object System.Management.Automation.AuthorizationManager "Microsoft.PowerShell"))} Disable-ExecutionPolicy

I found this here: –> https://blog.netspi.com/15-ways-to-bypass-the-powershell-execution-policy/

Citrix PVS device BSOD 0x0000007B via SCCM build

 

After installing the Citrix PVS Target Device software via SCCM or some other command line tool the Provisioning Services Target Device software:

%drive%\%folder%\PVS_Device_X64.exe /s /v /qn /norestart

What can happen is via the command line installation (not via the GUI) the files are not copied to the correct place. The quick fix is after the install, via a new command line:

Copy “C:\Program Files\Citrix\Provisioning Services\drivers\*.*”  to “%windir%\System32\Driver”

Then copy the image to the PVS and good to go.

 

 

"Dave Colvin"

PVS Automation with PowerShell

 

The script support installs when you install the Desktop Delivery Controller and PVS console.

1. Install the Desktop Delivery Controller and PVS consoles (or the powershell MSIs)
2. Add-PSSnapin *Citrix*,*PVS*
3. Installing Microsoft’s Remote Server Administration Tool(RSAT) Active Directory Support
4. Import-Module ActiveDirectory

The Provisioning Services cmdlets are installed via a 2 step process.

1. Run the following command to install the MCLIPSSnapin for the PVS cmdlets:
2. C:\Windows\Microsoft.NET\Framework\v4.0.30319\Installutil.exe “C:\Program Files\Citrix\Provisioning Services Console\MCLiPSSnapin.dll”
3. Add-PSSnapin MCLiPSSnapin

Now you have come this far some interesting commands:

Get all Devices in

Mcli-Get Device

Get devices in collection

MCLI-Get Device -p collectionName=”COLLECTIONNAME”,siteName=”SITENAME”

Add a device

MCLI-add Device –r devicename=xxxx1, deviceMac=00-xx-00-xx-00-xx, description=”something”, collectionName=”coll name”, siteName=”your site”

Get device details

MCLI-get Device –p devicename=xxxx1

Delete a device

MCLI-delete Device –p devicename=xxxx1

Add existing vDisk to store

MCLI-Add diskLocator -r diskLocatorName=”VDISKNAME”,siteName=”SITENAME”,storename=”STORENAME”

Add the target device to its device collection and create a computer object

Mcli-Add Device -r deviceName=$VM_Name, collectionName=$collection, siteName=$site_1, deviceMac=$MAC, description=$description, copyTemplate=1
Mcli-Run AddDeviceToDomain -p deviceName=$VM_Name, organizationUnit=$OU

Tips and Trick for Citrix PVD

 

• Is PvD compatible with XenApp?
• No only XenDesktop

 

• Is a PvD the same as a differential disk?
• No, PvD operates at the object level (files, folders, and registry). This enables all the changes that have been captured to persist across a base image updates whereas a differential disk would become invalidated in the case of a base image update.

 

• Can multiple PvDs be associated to a device/user?
• There can only be one PvD per Virtual Machine. The PvD is assigned to a Virtual Machine when building the catalogue of desktops. The pool type for a PvD catalogue is a pooled static, which the desktop is assigned to the user on first use.

 

• Is the PvD a 1-1 mapping per user?
• It is a 1:1 mapping to a Virtual Machine in a catalogue (assigned to the user on first use). The administrator can move a PvD to a new virtual machine in a recovery situation.

 

• If you create a catalogue for pooled with PvD, it does not mean that the user is always required to be assigned to that Virtual Machine defeating one of the benefits of a pooled?
• The base image is still shared and updated across the pool. However, once the user makes an initial connection to a Virtual Machine, the Virtual Machine is kept assigned to the user.
  Note: You must connect early in the starting stage long before you know who the user is in order to maximise the application compatibility for services, devices etc.

 

• Should the paging file be captured on the PvD?
• No. If you try to configure it this way, then the PvD will ignore this and will use the base Virtual Machine image (or Diff disk).

 

• Do I still require Profile Management?
• Personal vDisk does not roam. So if you have users that require profile roaming, you must use a roaming profile solution with PvD. It has been tested and supported with Citrix Profile Management.

 

• Does a PVD roam or is it assigned to single desktop?
• A PvD is attached to a Virtual Machine or machine, which is then assigned to the user. The administrator might move a PvD to a new machine in recovery situations.

 

• How do you configure Personal vDisk later if you choose not to enable it during the Virtual Desktop Agent (VDA) meta-installer?
• Run the inventory updater in the base image through the start menu shortcut (or “Ctxpvd –s inventory”), which results in the service being started or inventory taken. At this point, the service is enabled and ready to run inventory and manage the PvDs.

 

• Is the drive letter used by PvD able to be hidden?
• PvD currently uses two drive letters. The v: drive is hidden and is a blended view of the c: drive.
  The P: drive is not hidden.

 

• I cannot see v: drive; is there a way to see it?
• v: is only visible at a command prompt window. However, it is a blended view of the c: drive and appears to be identical. There is no way within the OS to see what is really on the base c: drive and what is on the PvD (P: drive).

 

• Is the UserData.vhd file inside the P: drive mounted as v:?
• The disk that is attached at the hypervisor is mounted as P:. The P: drive is where the user profile is redirected and captured. Also located on that P: drive is a UserData.vhd that is mounted as v:.
• The V: drive is where all the non-profile data attempting to write to the base Virtual Machine is redirected and stored. v: is visible from command prompt windows but not from Windows Explorer.

 

• How do I change PvD to use different drive letters?
• The P: drive might be changed in Desktop Studio when creating the catalogue. This should only be changed before usage since changing afterwards might lead to various errors (same as changing the c: drive to another letter after installation). 
  The v: drive must be changed in base image before being used in a catalogue:

KEY: HKLM\SOFTWARE\Citrix\personal vDisk\Config

VALUE: VHDMountPoint
Example: V:\

Note: Drive conflicts leads to failures.

• What is captured on the v: drive and what is capture on the P: drive?
• The P: drive is the vDisk that is attached to the hypervisor to the Virtual Machine. It contains the user’s profile is redirected (c:\users … ). It also contains the UserData.vhd file that is in turn mounted as the v: drive.

 

• The v: drive is where the applications and machines state is captured.
• When resetting the PvD, you are resetting the v: drive (which is really restoring the UserData.vhd file on the P: drive to its original empty or template state.

To reset, the machine with the Personal vDisk must be running; however, the user does not have to be logged on to it.

When you reset the disk, the settings revert back to their factory default values and all data on it is deleted, including applications. The profile data is retained unless you modified the Personal vDisk default (of redirecting profiles from the C: drive).

From the Help Desk view, choose the targeted Desktop OS machine.
From this view or in the Personalisation panel of the User Details view, click Reset Personal vDisk.
Click Reset. After the user is logged off (if the user was logged on), the machine restarts.

If the reset is successful, the Personal vDisk status field value in the Personalization panel of the User Details view is Running. If the reset is unsuccessful, a red X to the right of the Running value appears. When you point to this X, information about the failure appears.

To reset the PvD from the Desktop Director console or run the following command from elevated command prompt on the VM:

“C:\Program Files\citrix\personal vdisk\bin\ctxpvd –s reset”

This would reset all User Data excluding Profile information, so in effect, a user would lose any applications installed.

 

If antivirus products are installed on your desktops, ensure the VHD is big enough to store antivirus definition files, which are typically large.

The presence of antivirus products can affect how long it takes to run the inventory or perform an update.

Target (w7):

• \Program Files\Citrix\Provisioning Services\BNDevice.exe
• \Program Files\Citrix\Provisioning Services\TargetOSOptimizer.exe
• \Windows\System32\drivers\bnistack6.sys
• \Windows\System32\drivers\CfsDep2.sys
• \Windows\System32\drivers\CVhdBusP6.sys
• Exclude scanning of Write Cache

Target – Personal vDisk:

• \Program Files\Citrix\personal vdisk\bin\CTXPVD.exe
• \Program Files\Citrix\personal vdisk\bin\CTXPVDSVC.exe
• \Program Files\Citrix\Personal vDisk\BIN\WIN7\

 

 

http://support.citrix.com/proddocs/topic/xendesktop-7/cds-manage-personal-vdisks.html

http://support.citrix.com/article/CTX131553

https://literallyvirtual.wordpress.com/?s=vdisk

http://blogs.citrix.com/2013/09/22/citrix-consolidated-list-of-antivirus-exclusions/

Copy a Citrix PVS Versioned Disk

 

If try and just cope the .VHD of a versioned vDisk you’ll get an error message about not disk found. What you need to do is copy more, rename, export and then import.

To simplify the process you can merge the VHD chain of the source vDisk or just copy more files now and do it after? Here is how:

• Copy all the versioned vDisk in the chain (*.vhd, *.ahvd, *.pvp NOT the *.lok)
• Rename the copied files as required

• Open the PVS console, right click the source vDisk, and choose ‘Export vDisk…’

• Choose the latest version in the ‘Export versions starting at’
• This creates a XML (manifest file) containing the entire information about the versions of that vDisk

• Rename the XML file
• Edit the XML file change all references of the source vDisk to the copied vDisk name
• You should have a set of VHD/AVHD/PVP/XML files with the same file name. And an XML which refers to the new VHD files
• Open the PVS console, right click the vDisk store, and choose ‘Add or Import Existing vDisk…’

• After a short delay a popup appears saying that the import was successful

Job Done.

 

Cheers Dave Colvin

http://dave.colv.in 

http://twitter.com/DaveColvin

Hat tip: http://www.out-web.net/?p=1177

Raspberry Pi + Windows 10 = IoT (at home)

 

The new Raspberry Pi 2. 6x the power, 1 GB RAM, Windows 10 support and the same price.

This Broadcom CPU has two distinct improvements over the BCM2835 of the RPi B+. First, it has quadrupled the cores, each running at 900 MHz. (PI B+'s single-core 700 MHz). Also included a small tweak that allowed them to support 1 GB of RAM, double the 512 MB on the other models.

Microsoft announced today that Windows 10 would run on the Pi 2 free for the developer community via the Windows Developer Program for IoT later this year. Windows 10 on the Raspberry Pi 2 will be the IoT SKU of Windows 10, not the full version, but that’s exactly what the device was designed for.

Microsoft says that it sees the developer community as the foundation of the next wave of computing. By offering Windows 10 at no cost Microsoft has guaranteed that Windows 10 will be used in all manner of cheap projects that it would have never been considered for if the OS was selling at prices like previous generations of Windows.

Register with Microsoft. Buy some Pi.

+ =

Updated Citrix Receiver 4.2 PNA like experience

 

This is what the new PNA like experience looks like in the Start Menu of Windows 7. You can also get this on the desktop (but I have not shown this).

To get this you need to install the 4.2 receiver with the following command line. I cant stress enough how specific the CAPS, format and order this command line is.

Replace the section in yellow with your storefront server, ALSO note the /discover in the command line (see below where you can get this exact link from the Storefront server .CR file).

CitrixReceiver.exe /silent ADDLOCAL="ReceiverInside,ICA_Client,SSON,AM,SELFSERVICE,USB,DesktopViewer,Flash,Vd3d" ENABLE_DYNAMIC_CLIENT_NAME=Yes ALLOWADDSTORE=S ALLOWSAVEPWD=S STARTMENUDIR=\CitrixXenApps\ /INCLUDESSON /STORE0="Store1;https://storefront.COLV.IN/Citrix/Store1/discovery;On;Store1"

REBOOT, you need this as the SSOSVR.EXE needs to be running as seen below.

Additionally you need all the following:

1. TO BE USING HTTPS and a valid Cert.
2. You need the XML trust in both XenDesktop OR older XenApp
3. Your StoreFront server needs to be in ‘Local Intranet’ or ‘Trusted Sites’ in IE
4. Enable “Automatic Logon with current user name and password” is enabled in local Intranet if that is what you are in (see above).
5. Enable “Automatic Logon with current user name and password” is enabled in Trusted Sites if that is what you are in (see above).

 

Once it works, IE should auto logon as shown below.

 

If you don't know the URL above in yellow download the .CR file and it is highlighted below

 

This is the connection receiver once installed.

 

To get the Start Menu to populate this is the command line. It should do it automatically on reboot.

"C:\Program Files (x86)\Citrix\SelfServicePlugin\SelfService.exe" –showAppPicker

Once working correctly the Citrix Receiver in the notification area should logon automatically.

 

This is an update from the older article http://davestechnology.blogspot.com.au/2013/12/you-want-back-pna-program-neighbourhood.html

XenDesktop and XenApp VDA Exclusion

 

The default Citrix Virtual Delivery Agent installation includes several optional components that may not required, for example when upgrading the v7/v7.1 VDA software. They can be excluded using an installation command line.

The options are:

• Personal vDisk
• Machine Identity Service
• Citrix User Profile Manager
• Citrix Universal Print Client.

The command line is:

• XenDesktopVDASetup.exe /EXCLUDE “Personal vDisk”, “Machine Identity Service”
• etc

There is no help on the command line, thanks Citrix !

Links

Upgrading VDA: http://support.citrix.com/proddocs/topic/xenapp-xendesktop-75/cds-xd-upgrade-xd7-to-7-1.html#manual-phys-vda-upgrade

Article about the VDA: http://support.citrix.com/article/CTX140972

Citrix PVS 7.6 Wizard crashes “application was unable to start correctly”

 

After installing Provisioning Server 7.6 on Windows 2008 R2 SP1 (patched to current) you start the Configuration Wizard you receive the following error: “The application was unable to start correctly (0xc01500002)”

This error is caused by the program requiring Visual C++ 2008 Redistributable Package.

Download and install it to run the PVS Configuration Wizard.

Package: https://www.microsoft.com/en-us/download/details.aspx?id=2092

 

Hattip: http://www.vdnieuwenhof.eu/knowledge-base/the-application-was-unable-to-start-correctly-0xc01500002-configwizard-exe/

Change Network Interface in Existing Host Connection with XenDesktop

 

Open PowerShell as asministrator.

asnp Citrix* to load Citrix Module.

dir XDHyp:\HostingUnits to get Host connection details.

The following is an example of the output for the preceding commands:

PSPath : Citrix.Host.Admin.V1\Citrix.Hypervisor::XDHyp:\Hosting
Units\SERVERXD01
PSParentPath : Citrix.Host.Admin.V1\Citrix.Hypervisor::XDHyp:\Hosting
Units
 
PSChildName: SERVERXD01
 
PSDrive : XDHyp
PSProvider : Citrix.Host.Admin.V1\Citrix.Hypervisor
PSIsContainer : True
HostingUnitUid : 9b0ee1f0-2b45-45d5-9664-8cad350130f8
HostingUnitName : SERVERXD01
HypervisorConnection : XSG7Pool
RootPath : XDHyp:\Connections\XSG7Pool\
RootId :
 
NetworkPath: XDHyp:\Connections\XSG7Pool\network1.network
 
NetworkId : d8f21da0-6697-4fce-925b-99c19d4bae70
Storage : {XDHyp:\Connections\XSG7Pool\iSCSI 500GB.storage}
VMTaggingEnabled : True
UseLocalStorageCaching : False
Metadata : {}

Copy PSChildName and NetworkPath from the output:

Set-Item -Path xdhyp:\hostingunits\PSChildName

NetworkPath xdhyp:\connections\XSG7Pool\NetworkName

For example, new network interface is Network2 for the host SERVERXD01

Set-Item -Path xdhyp:\hostingunits\XENSERVERXD01 -

NetworkPath 'xdhyp:\connections\XSG7Pool\Network2.network'

Citrix Receiver command line

 

if any of you have suffered the pain of trying to get all the switches to work when installing the Receiver 4.2 via command line syntax, some case sensitive some not!!, the command below works:

CitrixReceiver.exe ADDLOCAL="ReceiverInside,ICA_Client,Flash,USB,SSON" ENABLE_DYNAMIC_CLIENT_NAME=Yes ALLOWADDSTORE=S ALLOWSAVEPWD=S STARTMENUDIR=\CitrixXenApps\ /INCLUDESSON /STORE0="Store1;https://storefront.colv.in/Citrix/Store1/discovery;On;HR Store1"

Citrix XenApp 7.x VDA Registration State stuck in Initialising

 

On October 16th, 2014 Jason Samuel did a really good post on this with a script to restart the affected service on the affected servers.

On XenApp 7x, you notice the registration state of the machine is stuck on “Initializing” in Citrix Studio and no one will be able to launch any apps.

The work around is to restart the “Citrix Desktop Service” on the impacted server.

http://www.jasonsamuel.com/2014/10/16/citrix-xenapp-7-x-vda-registration-state-stuck-in-initializing-and-a-self-healing-powershell-script-to-fix-it/

 

 

 

Cheers

Dave Colvin, http://dave.colv.in

The VPN client agent was unable to create the interprocess communication depot

 

When attempting to install the Cisco AnyConnect client for UI Anywhere access, you receive the following error message:

The VPN client agent was unable to create the interprocess communication depot.

To resolve this issue:

• Click on View Network Status and Tasks.
• Click on Change Adapter Settings.
• Right-click the shared connection and choose Properties
• Click the Sharing tab
• Clear the Allow other network users to connect through this computer’s Internet connection checkbox
• Click OK.

 

Continue the install. No reboot required.

Change XenDesktop 7.6 SQL Server

If you setup the SQL Express edition and need to move it for production. This is how.

Open PowerShell as and Administrator:

Add-PSSnapin Citrix*
Get-LogDataStore
Get-MonitorDataStore

They BOTH output something like this:

ConnectionString : Server=XDC-PROD01\SQLEXPRESS;Initial Catalog=CTX-XD7-PROD;Integrated Security=True

DataStore        : Site


DatabaseType     : SqlServer


Provider         : MSSQL


SchemaName       : Monitor


Status           : OK

ConnectionString : Server=XDC-PROD01\SQLEXPRESS;Initial Catalog=CTX-XD7-PROD;Integrated Security=True

DataStore        : Monitor


DatabaseType     : SqlServer


Provider         : MSSQL


SchemaName       : MonitorData


Status           : OK

Copy the contents of the BOLD above to a string and change the server name and instance details with server= in the prefix.

$CS = “server=REMOTE-PROD01\SQL02;Initial Catalog=CTX-XD7-PROD;Integrated Security=True”

• Set-LogSite -State Disabled



• Set-LogDBConnection -DataStore Logging -DBConnection $null



• Set-MonitorDBConnection -DataStore Monitor -DBConnection $null



• Set-MonitorDBConnection -DBConnection $null



• Set-AcctDBConnection -DBConnection $null



• Set-ProvDBConnection -DBConnection $null



• Set-BrokerDBConnection -DBConnection $null



• Set-EnvTestDBConnection -DBConnection $null



• Set-SfDBConnection -DBConnection $null



• Set-HypDBConnection -DBConnection $null



• Set-ConfigDBConnection -DBConnection $null –force



• Set-LogDBConnection -DBConnection $null –force



• Set-AdminDBConnection -DBConnection $null –force

Move the database between the servers.

On the SQL server create the account(s)

sqlcmd -S env3-sql2\AON -q "create login [domainName\ddcName$] from windows"

set-ConfigDBconnection -dbconnection $cs

set-AdminDBconnection -dbconnection $cs


set-LogDBconnection -dbconnection $cs


set-AcctDBconnection -dbconnection $cs


set-BrokerDBconnection -dbconnection $cs


set-EnvTestDBconnection -dbconnection $cs


set-HypDBconnection -dbconnection $cs


set-MonitorDBconnection -dbconnection $cs


set-ProvDBconnection -dbconnection $cs


set-SfDBconnection -dbconnection $cs


set-LogDbConnection -DataStore logging -DbConnection $cs


set-MonitorDbConnection -DataStore monitor -DbConnection $cs


set-LogSite -State Enabled

 

Nokia 1020 camera verses IPhone 6

 

With two photos taken in the same spot within a minute, no options, just default point and shot. With my none scientific methods I think the Nokia 1020 still has the better image colours, and of course the resolution / reframe options. So the winner - Nokia 1020 !

Zoomed in 300%

Nokia 1020 High Res

IPhone 6

Nokia 1020 Standard (social media res)

Zoomed out to 25%

Nokia 1020 High Res (was still too large for frame the top is cut)

IPhone 6

Nokia 1020 Facebook Quality

1000 Pixels wide cropped

Nokia 1020 High Res	IPhone 6	Nokia 1020 Facebook

Citrix StoreFront 2.6 error on first use - ManagedPipelineHandler

 

If you get the error, on Windows Server 2008 R2:

HTTP Error 500.21 – Internal Server Error.
Handler "DefaultPageHandler" has a bad module "ManagedPipelineHandler" in its module list

Run the command:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

To reinstall\re-register asp.net

Press F5 to refresh.

hat tip: http://discussions.citrix.com/topic/349746-storefront-25-installation-issuesplease-help/

Citrix StoreFront for dummies (v2x)

StoreFront key components

Authentication service: An integral part of StoreFront,  authenticates users to XenDesktop sites, XenApp farms. The authentication service ensures that users only need to log on to StoreFront/Receiver once.

Store: Retrieves user credentials from the authentication service to authenticate users to the components providing the resources. The store enumerates and aggregates the resources currently available from XenDesktop sites, XenApp farms. Users access the store through Citrix Receiver or a Receiver for Web site.

Application Subscription Store (Data Store):This store saves and indexes the application or desktop subscriptions of the users on a per - StoreFront Store basis. Tthe new Application Subscription Store uses the built-in Microsoft Windows Extensible Storage Engine to store details of users’ app subscriptions locally on StoreFront servers. When joining a StoreFront server to a Server Group the replication of data between all members is configured automatically.

Receiver for Web site:This site enables users to access stores through a webpage. If a version of Receiver installed locally it can be upgrade or if not detected it can be installed. Where Receiver cannot detected or installed the HTML5 client can start in compatible web browsers (IE over HTTP, Chrome/Firefox over HTTP/S).

Desktop Appliance site: Desktop Appliance sites provide users of non-domain desktops with an experience similar to that of user with domain-joined desktops. The web browsers is configured to start in full-screen mode displaying the logon screen for a Desktop Appliance site.

XenApp Services site: Used as a service to support PNAgent (Receiver for Enterprise), seamless desktop experience, Fast Connect, and Desktop Lock for repurposed PCs. or other devices like IPAD etc.

Authentication to StoreFront

1. User enters username and password on StoreFront server. The authentication service validates (the user credentials) with a domain controller.
2. StoreFront checks the data store for existing user subscriptions and stores them in memory
3. StoreFront forwards the user credentials as part of a XML query to the backend XenApp / XenDesktop
4. Delivery Controller validates (the user credentials) with a domain controller
5. Delivery Controller checks which resources have been published to this user within its database
6. Delivery Controller sends an XML response to StoreFront which contains all resources available for the user from the XenDesktop site
7. StoreFront sends the list of available resources including the existing subscriptions to the Citrix Receiver installed locally or displays them in Receiver for Web

A Non blank interface for new users

To avoid users from having a blank screen when they first logon, automatically subscribe users to a few core applications. Add KEYWORDS:Auto to the application or desktop description in XenApp or XenDesktop. Another option that can be used to organise applications is KEYWORDS:Featured. The Featured keyword only places apps in the Featured category

Local apps used via StoreFront

In addition the string KEYWORDS:prefer="application" can be used to specify that the locally installed version of an application should be used in preference to the equivalent delivered instance if both are available

Thanks to this white paper for the details, I have simplified it where I thought relevant : http://support.citrix.com/servlet/KbServlet/download/33432-102-697177/StoreFrontPlanningGuide.pdf 

Citrix HTML5 client on StoreFront Server

I put this together as official Citrix material is a bit ambiguous on what is needed, it is all there, but obtuse.

What is it? Receiver for HTML5 enables users to access desktops and applications directly within HTML5-compatible web browsers without needing to install Citrix Receiver.

StoreFront:

On the StoreFront use the Deploy Citrix Receiver task to configure the behaviour of a Receiver for Web site (HTML5 client) when a Windows or Mac OS X user without the Citrix Receiver installed accesses the site. By default, Receiver for Web sites automatically attempt to determine whether Citrix Receiver is installed when accessed from computers.

Specify the response of the Receiver for Web site if Citrix Receiver cannot be detected on a user's device.

• If you want the site to prompt the user to download and install Citrix Receiver but fall back to Receiver for HTML5 if Citrix Receiver cannot be installed, select Use Receiver for HTML5 if local install fails. Users without Citrix Receiver are prompted to download and install Citrix Receiver every time they log on to the site.
  
• If you want the site to enable access to resources through Receiver for HTML5 without download and install Citrix Receiver, select Always use Receiver for HTML5. With that option selected, users always access desktops and applications on the site through Receiver for HTML5, provided they use an HTML5-compatible browser. Users without an HTML5-compatible browser have to install the native Citrix Receiver.

XenApp and XenDesktop:

For local users on the internal network, access through Receiver for HTML5 to resources provided by XenDesktop and XenApp is disabled by default. To enable local access to desktops and applications using Receiver for HTML5, you must enable the ICA WebSockets connections policy on your XenDesktop and XenApp servers. XenDesktop and XenApp use port 8008 for Receiver for HTML5 connections.

Ensure your firewalls and other network devices permit access to this port.

Client browsers:

Receiver for HTML5 can only be used with Internet Explorer over HTTP connections. To use Receiver for HTML5 with Firefox over HTTPS connections, users must type about:config in the Firefox address bar and set the network.websocket.allowInsecureFromHTTPS preference to true.

PVS Soap service member of Local Administrators on Server

 

For PVS images that use KMS, when you switch modes from Private to Standard and select Key Management Service on the vDisk, the PVS server performs a volume operation on the server that requires elevated privileges, specifically the ability to perform volume maintenance tasks.

If you are running Soap/Stream as Network Service or a custom account, it not have the permissions required.

You can test the GPO \Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\ “Perform Volume Maintenance Tasks” but I have not.

 

Hat tip: http://pvsguy.com/2014/02/12/why-is-it-important-to-be-a-local-admin-in-pvs/

Snapshot of Active Directory in Windows Server 2012 R2

Open a PowerShell window and type:

• NTDSUTIL
• SNAPSHOT
• ACTIVATE INSTANCE NTDS
• CREATE

Note the GUID that is created (above mine is 4f54…….), or just leave the CMD prompt open. You can LIST ALL to see the GUIDs later.

QUIT and QUIT to exit from snapshot or you can mount that GUID

If you did quit, use

• NTDSUTIL
• SNAPSHOT
• ACTIVATE INSTANCE NTDS
• LIST ALL

If you  just enter the next command it is

• MOUNT YOUR-GUID-YOU-WANT

QUIT and QUIT to exit from the mount process

To start the ADDS and export files from it find the name of the snapshot with DIR C:\$*.*

Then start it up with

• DSAMAIN /DBPATH C:\$SNAP_date&time_VOLUMEC$\WINDOWS\NTDS\NTDS.DIT /LDAPPORT 6660

Leave DSAMAIN / CMD running in the background

Open Active Directory Users and Computers (or LDIFDE etc) and select CHANGE DOMAIN CONTROLLER YOURCOMPUTERNAME:6660

This is the old Active Directory from the backup.

Note what you need or export what you need etc.

When finished close the command prompt or press CTRL+C to stop DSAMAIN.EXE

To close the open snapshot issue the following commands

• NTDSUTIL
• SNAPSHOT
• ACTIVATE INSTANCE NTDS
• LIST ALL
• UNMOUNT YOUR-GUID
• QUIT, QUIT

Done. Now you just need a daily, weekly task to do the backup.