SCCM report for citrix receiver versions

Following report provides all the installed versions of Citrix receiver and also removes;
             Citrix Receiver (HDX Flash Redirection);
             Citrix Receiver Updater;
             Citrix Receiver(DV);
             Citrix Receiver(SSON);
             Citrix Receiver Inside and Citrix Receiver(Aero).
This report limits to a particular collection. Change the collection ID as required.

**************************************************************************
 SELECT DISTINCT
                      sys.Netbios_Name0 AS [Machine name], sys.User_Name0 AS [User name],
arp.DisplayName0 AS [Application Name], arp.Version0 AS [Application version]
FROM  v_R_System AS sys INNER JOIN
             v_GS_ADD_REMOVE_PROGRAMS AS arp ON sys.ResourceID = arp.ResourceID INNER JOIN  v_FullCollectionMembership AS fcm ON sys.ResourceID = fcm.ResourceID
WHERE     (arp.DisplayName0 LIKE '%Citrix receiver%') AND (fcm.CollectionID = 'LAB000132') AND (arp.DisplayName0 NOT LIKE '%Citrix Receiver (HDX Flash Redirection)%') AND
          (arp.DisplayName0 NOT LIKE '%Citrix Receiver Updater%') AND (arp.DisplayName0
NOT LIKE '%Citrix Receiver(DV)%') AND 
(arp.DisplayName0 NOT LIKE '%Citrix Receiver(SSON)%') AND (arp.DisplayName0
NOT LIKE '%Citrix Receiver(USB)%') AND (arp.DisplayName0 NOT LIKE '%Citrix Receiver Inside%') AND 
(arp.DisplayName0 NOT LIKE '%Citrix Receiver(Aero)%')
***************************************************************************
 More SCCM custom reports can be found here

HResult 0xFFFFFFFF, Level 16, State 1

HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.

When running sqlcmd on the local machine where SQL server is installed and in the command if we use  sqlcmd –S (localhost\SQLINSTANCE) –i C:\filepath\sqlquery.sql
we get above error.

To resolve the problem change command line to;
sqlcmd –S localhost –i C:\filepath\sqlquery.sql

Make sure -S is in uppercase and -i is in lowercase.

Task Sequence failed with error code 0x80070652

Most likely you are getting this error when running an application installation task sequence where the task sequence have multiple applications and a reboot involved in between.

The SMSts.log will show;
Installation failed with error (0x80070652)

Install software failed, hr=0x80070652

Another installation is already in progress. Complete that installation before proceeding with this install. (Error: 80070652; Source: Windows)

As the error msg shows, there may be an other installation in progress specially previously installed software before the reboot. Because of the SMShost service delay start, the task sequence won’t start straightaway after the reboot. Meanwhile, the software installed before the reboot will start doing something (re-configuration or perhaps installing updates). When the SMSHost service starts, it identifies other installation running so the installer fails. Hence the above error msg.

To resolve the problem, you need to identify which application is causing the problem then modify the installation.

Remote Connection to WinPE during SCCM OSD Task Sequence

Some or the other times, we need to help out the field guys / deployment engineers in a remote site with OS deployments.
And more often we feel like, troubleshoot our self rather asking them to run the commands. Well, here is an easy way of remote controlling an OS deployment task sequence session when running WinPE.
 
1.    Download winvnc binaries
2.    Launch winvnc.exe
         2.1    Display Query Window is unchecked
         2.2    Set a password
         2.3    Click OK to close the winvnc.exe
3.    Now there will be an additional file ultravnc.ini created
4.    Open the ultravnc.ini file then look for path then change to X:\Windows (This is the path where it will be running from)
5.    Create a package in SCCM without a program
6.    After “Restart in Windows PE” step create a new group called WinPE Remote
       6.1    Add a Run Command Line step and type wpeutil DisableFirewall
       6.2    Copy the VNC package to the WinPE  by adding Run Command Line Step
                      xcopy.exe ".\*.*" "%WinDir%\VNC" /E /C /Q /H /R /Y /I
                 Browse to the package and Select the VNC package which was created in step 5
       6.3    Add another Run Command Line step to launch the winvnc.exe
                     cmd.exe /c start %windir%\VNC\winvnc.exe
7.    Launch vncviewer.exe on the local computer and enter the IP address of the destination 
        computer.
8.    Enter the password on the prompt
9.    That’s it. You have access to OSD image deployment screen

Limitations:
1.    We should know the IP Address of the destination computer
2.    Once the machine reboots, will lose the connection

The detected setup program architecture does not match the current boot image

The detected setup program architecture does not match the current boot image. You must correct your task sequence so that the installation package matches the boot image.
 
Unspecified error (Error: 80004005; Source: Windows)

A task sequence fail with error code 80004005 when wiping the destination drive.
The smsts.log file (X:\Windows\Temp\SMSTSLog\smsts.log)file display above error msg.

The reason for this message is, using incorrect boot image then the detected target Operating System architecture.
If deploying Windows 7 x86, we should be using x86 boot image for that task sequence. Otherwise the task sequence will fail with above error message.

Note; we can use different version of package to start a task sequence. However the task sequence should have assigned the correct boot image

SCCM 2012 application catalog 404

While working on a project, I ran into a problem with App Catalog.
When I manually typed the application Catalog path in a browser, received -
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

When accessing application Catalog from the software center, received -
“Cannot connect to the application server.”
The website cannot communicate with the server. This may be a temporary problem. Click the Retry action to submit your request again. If this problem continues, try again later, or view the “More Information” section to see details about the problem.

Based on the error msg’s, it is obvious that there is a problem with the installation of the application Catalog.
To review the status of the application Catalog open SMSAWEBSVCSetup.log from %SCCM_drive%\Program Files\Microsoft Configuration Manager\Logs\

I have noticed following error msg in SMSAWEBSVCSetup.log
Error: IIS ASP.NET is not registered
Installation Failed. Error Code: 126

So the problem is with the registration of ASP .NET
To register ASP .NET, Navigate to "C:\Windows\Microsoft.NET\Framework\v.4.0.30319\” and run “aspnet_regiis.exe –i “

So the command is: C:\Windows\Microsoft.NET\Framework\v.4.0.30319\aspnet_regiis.exe –i

This has resolved the application Catalog website issue.