Search This Blog

Friday, December 19, 2014

Globeteam er klar til endnu mere nyt blod

 

Nu er det jo heldigvis ved at være jul og tid til at takke alle for året, der er gået.

 

Tak til alle jer, der har besøgt min blog i løbet af det sidste år. Der er lige i øjeblikket omkring 20.000 side visninger om dagen.

 

Jeg håber at bare lidt af indholdet kan bruges af andre end mig selv J

 

I samme omgang synes jeg også, det er på sin plads at takke alle kunder, konsulenter og partnere, der på den ene eller anden måde har samarbejdet med Globeteam i år. Uden jer gik det jo slet ikke.

 

Vi er nu 30 dedikerede konsulenter i Infrastruktur gruppen, og vi har et mål om at vokse med yderligere 6 konsulenter til næste år.

 

Så hvis du arbejder med Infrastruktur på et af følgende områder: Citrix, VMware, Azure, Office 365 eller Microsoft generelt og samtidig er udadvendt og god til at skabe tilfredse kunder, så overvej om Globeteam ikke skulle være dit næste karriere trin. Se mere om vores forretnings model på http://globeteam.com/om-globeteam/unik-forretningsmodel/

 

Du er altid velkommen til at sende dit CV eller kontakte mig for en uformel snak.

 

Rigtig glædelig jul og godt nytår – vi ses derude i 2015.

Thursday, December 18, 2014

Changing Windows Login Screen Background

Sometimes I need to change the standard Login Screen background to for example a corporate logo.

Windows 7

We can easily do this from a SCCM task sequence during OSD.

First we need a jpg file with the image we want to use, this file must not be greater than 256 KB and called backgroundDefault.jpg

Next create a package with only the jpg file in SCCM.

Windows 7 will use our new background if we do these two steps in our task sequence:

First we create the registry value HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background\OEMBackground and set it to a dword value of 1.

Registry example:

image

We can do this using the command:

reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background /v OEMBackground  /t REG_DWORD /d 1 /f

SCCM Task Sequence example:

image

Then next we need to copy the file to the local Windows 7 installation, using the package with the jpg file:

image

File copied to the local folder:

image

Windows 7 login screen with custom background:

image

Windows 8

On windows 8 we can use Group policy Settings or a local policy.

Computer Configuration – Policies – Administrative Templates – Control Panel – Personalization – Force a specific default lock screen image

We can use a UNC path or a local path, if we are using a local file the file must of cause exist on the computer. Deploy this with the OSD task Sequence just like Windows 7.

image

Computer Configuration – Policies – Administrative Templates – Control Panel – Personalization – Prevent changing lock screen image

image

Settings enabled in the GPO:

image

 

Please note that Windows 8 requires Windows 8 and Windows Server 2012 cumulative update: November 2012 as explained here http://support.microsoft.com/kb/2787100/en-us

It also looks like Windows 8 must be activated before this will work.

Windows 8 lock screen with custom background:

image

Tuesday, December 2, 2014

Download fails with error 80072ee2

Sometime I have problem with packages not downloading and in smsts.log I get this error.

Download() failed, 80072ee2.

image

The only way I have found to fix this when it happen are to use the variables

SMSTSDownloadRetryCount = 5

SMSTSDownloadRetryDelay = 15

Set the at the top in your Task Sequence as shown here, and the problem I had diapered.

I would like to know the reason and what the problem is, so let me know if you got an idea Smile

image

image

Monday, November 24, 2014

Publishing operation failed because the console and remote server versions do not match

You might see this error when trying to publish a Secunia update to WSUS:

Failed to publish package

Code -2146233079

Publishing operation failed because the console and remote server versions do not match

image

This error can also be seen if you are using SCUP.

The problem is that the server were we are trying to do the publish from does not match the version at the WSUS server.

If you go to Installed Updates and find Windows Server Update Services 3.0 SP2, you will be able to se the currently installed updates on this server.

image

Do the same on the WSUS server and compare the installed updates:

image

In this example, the server with only the WSUS administrative console installed, is updated with http://support.microsoft.com/kb/2828185, but the WSUS server is only at http://support.microsoft.com/kb/2734608.

In order for this to work they must be at the same level.

Friday, November 14, 2014

Hotfixes that breaks OSD

Once again I have found my self in a situation where a customer had problems with a task Sequence stopping, so now it’s time to do a post about this well known situation

You might see your Task Sequence stopping with the following error in smsts.log:

Failed to set log directory. Some execution history may be lost. The system cannot find the file specified. (Error: 80070002; Source: Windows)

And also a statement saying Task Sequence environment not found. Not highlighted in red by default

image

The problem is well documented in the support case here : KB2894518

If a Microsoft System Center Configuration Manager task sequence that uses the "Install Software Updates" step installs a software update that triggers multiple restarts after the task sequence successfully runs the Install Software Updates task, the task sequence can fail.

The first restart that is initiated by the software update is controlled by the task sequence. However, the second restart request is initiated by a Windows component (typically, Component-Based Servicing) and therefore is not controlled by the task sequence. Because the second restart is not controlled by the task sequence, the task sequence execution state is not saved before the restart. When the task sequence resumes after the second restart, no state is available to continue successfully.

Unfortunately the support case is not updated the moment an update requiring multiple restarts are released, so note this issue so that you know what's going on the next time you see this error.

image

Thursday, November 6, 2014

Identify VMM RU4 installation

Microsoft has release Update Rollup 4 for System Center 2012 R2 Virtual Machine Manager http://support2.microsoft.com/kb/2992024.

Let’s take a look on how we identify the versions installed.

First the administrative console, you can see the current version by selecting about in the console:

image

After the RU4 update for the console has been installed you should see version 3.2.7768.0:

image

Before updating my console showed version 3.2.7672.0 for CU3:

image

You can also see the installed update by looking in installed Updates with RU4 you should see

Update Rollup4 for Microsoft System Center Virtual Machine Manager Administrator Console (x**) (KB2992023):

image

You can find the current version for the VMM server by right clicking the server in the console and selection Properties:

image

After updating the server with RU4 you should see version 3.2.7768.0:

image

Before I updated my server the version was 3.2.7672.0 for RU3:

image

The Server update is also visible in installed Updates, when RU4 is installed you should see

Update Rollup 4 for Microsoft System Center Virtual Manager Server (x64) (KB2992024):

image

The VMM agent version on your Hyper-V servers can be found by right clicking the Hyper-V server and select Properties.

If you have chosen to display the column Agent version you can see it directly on the host (Blue box):

image

After the VMM agent has been updated to RU4 you should see version 3.2.7768.0:

image

Before I updated the VMM Agent it showed 3.2.7672.0 for RU3:

image

You can use the Update Agent command to update your Hyper-V hosts:

image

The VMM Agent version can also be found in Programs and Features on the Hyper-V host:

image

And finally we should check the installation of Microsoft System Center Virtual Machine manager DHCP Server (x64) on the Hyper-V hosts, we can do this by a PowerShell command:

Get-WmiObject -Class win32_product -Filter 'Name = "Microsoft System Center Virtual Machine Manager DHCP Server (x64)"'

Before updating my Hyper-V server had installed version 3.2.7672.0 which is the RU3 version.

image

After upgrading to the RU4 version the PowerShell command returns version 3.2.7768.0:

image

You can also here find the same information in Programs and Features on the Hyper-V host:

image

The MSI file for installing the updated version of the System Center Virtual Machine Manager DHCP Server (x64) component can be found on your VMM server after updating the server to RU4

C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\SwExtn (depending on were you installed VMM but this is default):

image

Wednesday, October 22, 2014

Time to Upgrade Windows 10 from build 9860 to 9878

Update 14-11-2014

Build 9879 is available, the update procedure is the same as last time, you just need to change your update pace to fast:

image

This time there the enterprise version is also available as a ISO file, in order to download this go here:

http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise?i=1

image

Original post

Microsoft has released a new build of Windows 10 called 9860, so how do we upgrade?

No ISO will be released for this new build so the only way is to use the build in upgrade feature.

Start by entering Windows update settings in the search field in the new start menu, and then click on Windows update settings in the top.

image

In PC settings select Preview builds and then Download now:

image

When the download is completed click Install now:

image

You can find the downloaded esd file in your Windows\SoftwareDistribution\Download folder, so here the size of the downloaded file is 2.7 GB.

image

You need to restart the computer:

image

Now wait for Windows to get ready Smile

image

And finally:

image

After the upgrade is completed you will see two new updates in windows update (KB3008956 and KB3010668), install the updates and you are ready to go (this will of course change over time Smile but valid 22-10-2014):

image

Tuesday, October 21, 2014

Remote Group Policy updates are visible to users

In Windows 2012 R2 we have a very nice feature in the Group policy Management Console were we are able to run GPUpdate on all computers in a OU.

image

image

image

On a OU holding for example RDS or Citrix servers this is very useful.

But there is just one problem, users will see a popup like this on their screen.

image

If we try to update a single computer using powershell from remote wee will se the same popup behavior.

Example:

Invoke-GPUpdate -computer xenapptest -force -randomdelayinminutes 0

image

The problem and solution is explained here http://support.microsoft.com/kb/2741537

We must update only the computer Policy using PowerShell and not the User part of the policy, and this is often exactly what we need.

Invoke-GPUpdate -computer xenapptest -force -target computer -randomdelayinminutes 0

image

And no update is shown by using this command.

You can check the GroupPolicy log on the Computer running the GPUpdate to see if its actually is taken place:

image