Search This Blog

Thursday, November 28, 2013

Disable Help Sticker notifications in Windows 8.1 GPO

Windows 8.1 introduces Help Stickers so we can learn how to work with the new features that the OS has to offer. The feature is great and can help you learn the new features quickly if you like the popups.

These help stickers are easy to recognize by their black/brown, red/orange and white colors.

If you would like to disable this feature in a Enterprise environment Microsoft has provided a GPO for this.

imageimage

In order to disable the popup in a GPO use

Computer Configuration – Policies –Administrative Templates – Windows Components – Edge UI – Disable help tips

image

Enabling this policy will disable the help sticker popup.

image

This policy is also available in user context.

image

Monday, November 25, 2013

Unknown Computers and Required Task Sequence that fails – Part 2

last time I took a look at the Unknown computer object created when a task sequence fail http://larslohmann.blogspot.com/2013/11/unknown-computers-and-required-task.html.

But in some situations this object is not created, let try to remove the network while WINPE is downloading:

image_thumb17

It will off course fail and if you try to PXE boot again we are back to No boot filename received :

image

Again the PXE log will show:

no advertisements found

No boot action.

Rejected.Not serviced.

This time we are unable to use Clear Required PXE Deployment because the computer is simply not shown in the GUI.

If we take a closer look at the table LastPXEAdvertisment, we will find the MAC address in the table.

image

So how are we going to be able to PXE boot this computer again?

One way could be to import a computer into SCCM with the MAC address, Clear the PXE of this machine and delete the computer again, this way it will be back to unknown without any previous PXE boot.

Another way is to delete the entry in the table Smile

Maybe there is something that I have overlooked, but should this really be a problem?

Please let me know if some of you got a better solution.

Monday, November 18, 2013

Unknown Computers and Required Task Sequence that fails – Part 1

When deploying a Required Task Sequence to unknown Computers in SCCM 2012, you might be unable to PXE boot the computer again if the installation fails for some reason. So lets take a closer look at the documentation:

If the computer fails to install the operating system image or the Configuration Manager client, an “Unknown” record for the computer is created and the computer appears in the All Systems collection.

If you try to PXE boot the Computer again you will get the error No boot filename received

image

This is because the computer is no longer unknown, probably not in the target deployment collection, and we also need to Clear Required PXE Deployment to be able to PXE boot the device again.

In the PXE log we will see information like:

no advertisements found

No boot action.

Rejected. Not serviced.

image

An Unknown computer object has been created in All Systems.

image

We can grab this type of computers with a query, this will make it possible to target them with the deployment and to clear the required PXE Deployment.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Unknown = 1

image

image

image

And here we go again:

image

I must say that I am not very keen on required task sequences but sometimes they are needed, stay tuned for Part 2  Smile

Thursday, November 14, 2013

ldentify if SCCM 2012 R2 hotfix 2905002 has been installed

Microsoft has released and update for System Center Configuration Manager 2012 R2 (SCCM) http://support.microsoft.com/kb/2905002

image

In order to identify if the update has been installed we can use these methods:

First let us take a look at the console, after the update the console reports version 5.0.7958.1000 which is the same as before the patch was applied to SCCM 2012 R2 RTM.

image

The Console update is instead listed in Control Panel as an Installed Update:

image

The site will still report version 5.00.7958.1000 after the update (SCCM 2012 R2 RTM).

image

But again we can find the update in Control Panel as an Installed Update, reporting 5.0.7958.1101:

image

If we take a closer look at TSCore.dll for the console or SCCM base, we will notice that this file has the updated version 5.0.7958.1101

image

The client will report 5.00.7958.1101 after the client has been updated.

image

Before updating the client reported 5.00.7958.1000 for a 2012 R2 RTM client.

image

Tuesday, November 12, 2013

Link: XenApp 6.5 Optimization and Tuning

Here are some good links to take a closer look at when planning a XenApp infrastructure:

 

Optimization Guide for Windows Server 2008R2 with XenApp 6/6.5

http://blogs.citrix.com/2011/12/06/optimization-guide-for-windows-server-2008r2-with-xenapp-66-5-%E2%80%93-available-now/

image

 

Citrix Guidelines for Antivirus Software Configuration

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

image

 

XenDesktop and XenApp Best Practices

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

image

 

Citrix XenApp on VMware Best Practices Guide

www.vmware.com/files/pdf/solutions/vmware-citrix-xenapp-best-practices-EN.pdf

image

Wednesday, November 6, 2013

Access is denied

You might se the error Access is denied when some users start a published application or desktop from XenApp.

image

This issue can be seen on users who are member of an extended number of groups, there is not a specific number because it depends on the current number of users on the XenApp server.

You could lower the number of groups the users is a member of, or as a workaround you can increase the Kerboros MaxTokenSize.

On your XenApp server(s) create a dword value under HKLM\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters and set the value 48000 (Decimal).

image

The servers must be restarted before the change will work.

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

http://support.microsoft.com/kb/938118/en-us