Search This Blog

Wednesday, September 14, 2016

Citrix Receiver for Windows 4.5.10018

Citrix has released a new version of Citrix Receiver for Windows, new version is 4.5.10018:

image

You will find ADMX/ADML files in the installation folder (C:\Program Files (x86)\Citrix\ICA Client\Configuration) or here https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html

Starting with Version 4.5, all Citrix Receiver for Windows template files are merged into a single file called receiver.adm / receiver.admx / receiver.adml.

image

Download installation file :

https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html

Changes is this version and documentation:

http://docs.citrix.com/en-us/receiver/windows/4-5.html

Nice to finally get a fix for [#LC4710], which has haunted me with more than one customer, se also this http://discussions.citrix.com/topic/375437-sessions-freezing-with-receiver-4408014/

A new version of the 4.4 receiver has also been released 4.4.2000.16 (LTSR - Logon required)

image

https://www.citrix.com/downloads/citrix-receiver/receiver-for-windows-ltsr/receiver-for-windows-ltsr_4_4_2000

http://docs.citrix.com/en-us/receiver/windows/4-4/receiver-windows-44-about/receiver-for-windows-4-4-fixed-issues.html

Thursday, July 7, 2016

WSUS server crash

You might see that your WSUS server will crash after KB3159706 is installed.

The event log will report event ID 507 Update Services failed its initialization and stopped.

image

In the support article you will se that manual intervention is required, but since the update is pushed from Windows Update and WSUS itself, you might not be aware of the change.

Manual steps required to complete the installation of this update

Open an elevated Command Prompt window, and then run the following command (case sensitive, assume "C" as the system volume):

"C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing

image
Select HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features wizard (if not already installed).

image

Restart the WSUS service.

image

If SSL is enabled on the WSUS server you need to do a few more changes as explained in the support article KB3159706

And as always remember proper maintenance on the server:

Software update maintenance in System Center 2012 Configuration Manager

Wednesday, June 8, 2016

System Center Configuration Manager Cmdlet Library 5.0.8373.1189

Microsoft has released a new update for the SCCM cmdlet Library 5.0.8373.1189

image

Release History:

6/6/2016 - Update Release, version 5.0.8373.1189. Contains bug fixes
5/16/2016 - Update Release, version 5.0.8373.1182. Contains bug fixes and support for Configuration Manager (current branch - version 1602)
1/25/2016 - Update Release, version 5.0.8328.1155. Contains bug fixes and support for Configuration Manager (current branch - version 1511)
9/9/2015 - Update Release, version 5.0.8249.1128. Contains bug fixes and support for Configuration Manager SP2/R2 SP1
4/13/2015 - Initial Release, version 5.0.8231.1004.

Update check logic

In previous releases, the check for an updated version of the Cmdlet Library was performed on cmdlet execution if a certain time limit had passed. This check now occurs only when a new CMDrive instance is created. This change was made to reduce the number of warnings that may be written when there is an update available. For more information on this feature and how to configure it, please see the documentation at https://technet.microsoft.com/en-us/library/dn958404.

Download link

The System Center Configuration Manager Cmdlet Library Documentation

 

image

image

Thursday, May 19, 2016

Task Sequence error code (0x80070002)

You might se this error when deploying Windows from a SCCM 1511 task Sequence:

Task Sequence: xxx has failed with the error code (0x80070002)

image

If we take a closer look at the smsts.log file, you will in this specific case find the message No credential information in environment.

image

The reason will probably be that no Network Access Account has been defined, go to Administration, Overview, Site Configuration, Sites, in the top select Configure Site Components and Software Distribution.

image

Select the tab Network Access Account, an enter a account to use when access network locations.

image

See more information about this account here https://technet.microsoft.com/en-us/library/hh427337.aspx (search for Network Access Account)

Also see this post http://larslohmann.blogspot.dk/2016/01/task-sequence-error-code-0x80070002.html for another possible solution for the same error.

Monday, May 9, 2016

Citrix Receiver for Windows 4.4.1000.16 (CU1)

Citrix has released a new version of Citrix Receiver for Windows, new version is 4.4.1000.16 (CU1)

image

You will find ADMX/ADML files in the installation folder (C:\Program Files (x86)\Citrix\ICA Client\Configuration) or here https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html

image

Download installation file :

https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html

Changes is this version and documentation:

http://docs.citrix.com/en-us/receiver/windows/4-4.html

Thursday, April 28, 2016

Windows 10 and Office 2013

When deploying Windows 10 and Office 2013 with SCCM (here 1602) you might see that the update progress stops and the task sequence hangs.

image

If you take a closer look at the WUAHandler.log you will also notice that the installation progress has stopped.

image

Opening the event viewer will reveal that updates are actually still being installed.

image

Right now one workaround is to wait for all updates to be installed.

This is when you no longer see updates being installed in the Event Viewer and the Windows Update service change status to stopping.

Now the task sequence will hang for real.

image

Find the process ID for the Windows Update Service and terminate the process.

sc queryex wuauserv | find "PID"

taskkille /PID <ID from sc queryex> /F

image

This will of course change the status to not running.

image

The SMS Agent Host  will now change status to Stopping.

image

Stop this process as well:

sc queryex ccmexec | find "PID"

taskkille /PID <ID from sc queryex> /F

image

The task sequence should now continue:

image

Not pretty but ………..

Wednesday, April 20, 2016

Failed to load expression host assembly. Details: Could not load file or assembly 'SrsResources

If you choose to do an in place upgrade of SQL 2012 to SQL 2014 on your SCCM server, you might see this error when trying to run a report:

Failed to load expression host assembly. Details: Could not load file or assembly 'SrsResources, Culture=neutral' or one of its dependencies. The system cannot find the file specified"

image

And in Details:

image

The best way around this error is to remove the Reporting services point and add it again after it has been removed.

But if this is in a lab, here is a quick (and dirty) workaround:

Open the old Report Server BIN folder and copy srsresources.dll and the SCCMErrorResource (folder structure) default location will be C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin when upgrading from SQL 2012.

image

And paste the file and folders to the new Report Server BIN folder as shown here:

Default location will be C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\bin when upgrading to SQL 2014.

image

Now locate the file rssrvpolicy.config. Default location will be C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer for your new SQL 2014 Reporting server.

image

Edit the file and change the URL for srsresources.dll to the new location (just search for srsresources.dll to find the place to change)

Change from:

              <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin\srsresources.dll" />

Change it to:

              <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\bin\srsresources.dll" />

 

Save it and after a short wait period, try running a report again to test if its working as expected.

Tuesday, April 12, 2016

The version of the report server database is either in a format that is not valid, or it cannot be read

If you choose to do an in place upgrade of SQL 2012 to SQL 2014, you might see this error when trying to access the report server:

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '162'. (rsInvalidReportServerDatabase).

image

As part of a hotfix for SQL 2012 SP2 CU5, a change was made which resulted in a new ReportServer database version. Since this fix was made after the SQL2014 release, if your SQL2012 SP2 server is on CU5 or later, then it will have a higher database version than what SQL2014 RTM expects.

SQL 2014 SP1 has the same problem.

So if you see this problem upgrade to the latest CU level for SQL 2014 RTM or SQL 2014 SP1, and the problem will be fixed.

http://blogs.msdn.com/b/sql_server_team/archive/2015/03/20/upgrading-to-sql-2014-report-server-version-mismatch.aspx

While having this problem your SCCM console will just not display any reports (blank – no items found), so you will have to go to the  report server homepage URL to verify if this is your problem (as shown in the top):

image

Monday, April 4, 2016

Exchange 2013 and 2016 Schema versions

After an Exchange 2016/2013 installation and Active Directory schema change, several properties are updated to show that everything are as expected.

You can use the information in the following to make sure these properties have the right values.

Exchange Version

msExchProductId

rangeUpper

objectVersion (Microsoft Exchange System Objects)

objectVersion (Organization container)

Exchange 2013 RTM

15.00.0516.032

15137

13236

15449

Exchange 2013 CU1

15.00.0620.029

15254

13236

15614

Exchange 2013 CU2

15.00.0712.024

15281

13236

15688

Exchange 2013 CU3

15.00.0775.038

15283

13236

15763

Exchange 2013 SP1

15.00.0847.032

15292

13236

15844

Exchange 2013 CU5

15.00.0913.022

15300

13236

15870

Exchange 2013 CU6

15.00.0995.029

15303

13236

15965

Exchange 2013 CU7

15.00.1044.025

15312

13236

15965

Exchange 2013 CU8

15.00.1076.009

15312

13236

15965

Exchange 2013 CU9

15.00.1104.005

15312

13236

15965

Exchange 2013 CU10

15.00.1130.007

15312

13236

16130

Exchange 2013 CU11

15.00.1156.006

15312

13236

16130

Exchange 2016 Preview

15.01.0225.017

15317

13236

16041

Exchange 2016

15.01.0225.042

15317

13236

16210

Use an elevated powershell console to get the your values:

rangeUpper

Get-ADObject -Identity "CN=ms-Exch-Schema-Version-Pt,CN=schema,CN=configuration,DC=YourDomain,DC=YourDomainSuffix" -properties rangeUpper | select rangeUpper | format-List

image

msExchProductId

Get-ADObject -Identity "CN=YourExchangeOrganisation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=YourDomain,DC=YourDomainSuffix" -properties msExchProductId | select msExchProductId | Format-List

image

objectVersion (attribute on Organization container in Configuration Naming Context)

Get-ADObject -Identity "CN=YourExchangeOrganisation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=YourDomain,DC=YourDomainSuffix" -properties objectVersion | select objectVersion | Format-List

image

objectVersion (attribute on Microsoft Exchange System Objects container in Domain Naming Context)

Get-ADObject -Identity "CN=Microsoft Exchange System Objects,DC=YourDomain,DC=YourDomainSuffix" -properties objectVersion | select objectVersion | Format-List

image

Unsure about your Exchange Organization name?

Use the Exchange management Shell:

get-organizationconfig | select name,DistinguishedName | Format-list

image

For older versions and use of adsiedit.msc see http://larslohmann.blogspot.dk/2012/07/exchange-schema-version.html

Friday, March 25, 2016

Cannot obtain read/write access for install.wim

In some situations ICD can not do what you need, and because of that, you might still need a good old unattend.xml for Windows 10.

When opening a new install.wim in Windows System Image manager for the first time without a catalog file you will be asked if you want to create a new:

The catalog file for Windows 10 Enterprise Technical Preview cannot be opened for the following reason:

Cannot find the catalog file associated with the Window image Windows 10 Enterprise Technical Preview.

You must have a valid catalog file to continue. Do you want to create a catalog file?"

Technical Preview Smile https://twitter.com/mniehaus/status/666732194807742464

image

But when you answer Yes you might see this error:

Cannot obtain read/write access for install.wim.

In order to generate a catalog file, you must have read/write access to The Windows image file and its containing folder.

image

One explanation could be that the Install.wim is set to read-only, remove the Read-only mark and try again.

image

And the catalog file is now generated:

image

Thursday, March 17, 2016

Hi - We’re happy you’re here

When you logon to Windows 10 for the first time with a new user without a profile you will see this dialog:

Hi

 image

We’re happy you’re here

image

Lots of great features to get excited about

image

Getting everything ready for you

image

Let’s start

image

You might not like this dialog and prefer not to see it. setting the Group policy

Computer Configuration\Administrative Templates\System\Logon\Show first sign-in animation to disabled

image

Will change the dialog to this simple one (Preparing Windows):

image

You can also set this in unattened.xml as shown here:

image

    <settings pass="specialize">
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="
http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System /v EnableFirstLogonAnimation /t REG_DWORD /d 0 /f</Path>
                    <Order>2</Order>
                    <Description>Do not Show First Logon Animation</Description>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
    </settings>

Or directly in your task sequence with the command

reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System /v EnableFirstLogonAnimation /t REG_DWORD /d 0 /f