Hi,

I am running SCCM 2007 R2 SP2 and we have a couple of windows 8 and 8.1 based clients in our enviornment that we want to deploy packages to.

I see this hotfix http://support.microsoft.com/kb/2861663 adds support for the 8.1 clients but will it support the 8 based ones or do I have to apply this http://support.microsoft.com/kb/2750782 also to covers these?

Thanks...

Hi,

I will use the first one as it cover win8, win8.1 and win2012 server os.

The second one is much older, and when it was released perhaps Win8.1 wasn't released.

BR,

NB

Hi,

Great thanks, will do.

Also there is little information on how to apply this update from Microsoft.

Do you only install it on your primary site server?

It doesn't create a client package like the older KB for win 8.0.

Hi,

don't know if is creating a client package, but is no problem if is creating one, possible this client package has version of SCCM agent host higher then you have now for the other platforms (WinXp, Win7, Win2k3r2, win2k8r2). I didn't installed as we don't have yet Win8 OS in our infrastructure, I have installed updates for CM2012 SP1 CU1, CU2, and CU3 and all 3 hotfixes created a client package.

you can use that package to target collection where you have Win8, win8.1, win2012 server.

BR,

NB

Hi,

Ok I'm just going to install it on the primary site server only and see if I can then manage the Win 8 clients.

Thanks...

Hi,

Ok I've installed hotfix http://support.microsoft.com/kb/2861663 on the primary site server and secondary site servers.

Then I installed the SCCM client on the Windwos 8.1 client. I can see the client in the database and it's active but when I try to push an package to it it won't pick up the advertisement. The execmgr.log says 'Software distribution agent was enabled' but that's it.

Also it won't install Software Updates, the WUAHandler.log says

Scan failed with error = 0x8024401b.

OnSearchComplete - Failed to end search job. Error = 0x8024401b.

The locationServices.log and ClientLocation.log are ok.

The Windows Firewall on the Win 8 client is disabled.

Anybody seen this before?

Have you installed this? KB2734608

Hi, yes I have installed it.

Hi,

Ok I've installed hotfix http://support.microsoft.com/kb/2861663 on the primary site server and secondary site servers.

Then I installed the SCCM client on the Windwos 8.1 client. I can see the client in the database and it's active but when I try to push an package to it it won't pick up the advertisement. The execmgr.log says 'Software distribution agent was enabled' but that's it.

Also it won't install Software Updates, the WUAHandler.log says

Scan failed with error = 0x8024401b.

0x8024401b = Same as HTTP status 407 - proxy authentication is required.

Source: Windows Update Agent
-----

But before tackling that, http://support.microsoft.com/kb/2861663 states that there *is* a client patch package requirement but it isn't included in this KB (which is annoying and odd, but that's not uncommon...)

Note This update affects only those platforms that are included in the supported platforms list. The client part of KB 2750782 (SCCM2007AC-SP2-KB2698619-x86-ENU.msp) was originally released to provide support for Windows 8. However, it also applies to Windows 8.1 clients.

Hi,

Ok I've installed hotfix http://support.microsoft.com/kb/2861663 on the primary site server and secondary site servers.

Then I installed the SCCM client on the Windwos 8.1 client. I can see the client in the database and it's active but when I try to push an package to it it won't pick up the advertisement. The execmgr.log says 'Software distribution agent was enabled' but that's it.

Also it won't install Software Updates, the WUAHandler.log says

Scan failed with error = 0x8024401b.

  

0x8024401b = Same as HTTP status 407 - proxy authentication is required.

Source: Windows Update Agent
-----

We struck this issue when we introduced Win8.0 and CM12. It seems that because we use an authenticated proxy for our people to access the internet, and we also use WPAD and proxy.pac, that we uncovered a case-sensitivity issue, in that our SUP servername site system, was entered as FQDN.CONTOSO.COM but our proxy.pac file had only ever handled contoso.com, and, javascript processing of the proxy.pac is case sensitive all of a sudden for us.
We then found that no matter how we entered the fqdn into ConfigMgr, it automatically converts the case to upper, so we had no choice but to edit our corporate proxy.pac to handle both the cases. We opened a Premier case about the automatic upper-case conversion, and were told "that's how it is. file a DCR if you like&