Jump to content

SCCM 2012 R2 SP1 and SCCM 2012 SP2 now available (adds support for Windows 10)


Recommended Posts

Posted
Will need to raise a Change Request tomorrow to start the tedious process of being allowed to do this at work......
Posted
Good news! It took ages for SCCM 2012 to support Windows 8. It was literally months after.

 

90 days if I recall. Glad all MS divisions are starting to work together.

Posted
Is anyone else only getting a 1MB file when they try to download the 2012 R2 SP1 file? The 2012 file works OK, just not the R2 one.
Posted
Is anyone else only getting a 1MB file when they try to download the 2012 R2 SP1 file?

The larger of the two files for 2012 R2 is SCCM. The other is SCEP isn't it?

 

On my phone at the moment so can't check.

Posted
Has anyone got the update showing on their MS Volume Licensing site yet? Or is it okay to use the Technet Evaluation version to upgrade an existing installation?
Posted

Interestingly the SCEP client that comes with this SP is OLDER than the one I just got from WSUS?

 

SP1 Version: 4.7.213.0

WSUS Version: 4.8.204.0

Posted
The SCEP Client wfrom SP1 (Ver 4.7.213.0) now works with Windows 10

 

Or rather it installs, but the native Windows Defender seems to take over...

  • 2 weeks later...
Posted (edited)

Hi,

 

Whats the crack with these Service Packs, it talks about trails and stuff.

 

Also why is the 2012 R2 SP1 so small?

 

Thanks

Edited by FN-GM
Posted (edited)
What's the crack with these service packs, it talks about trials and stuff.

The service packs also double as evals (they won't convert your SCCM site into an evaluation version so you don't have to worry about that :) ). The non-eval service packs are downloadable from VLSC apparently.

 

Also why is the 2012 R2 SP1 so small?

 

http://blogs.technet.com/b/michaelgriswold/archive/2015/05/14/sccm-2012-sp2-and-r2sp1-from-here-to-there.aspx

 

What may confuse people is that R2 SP1 is a very small file. It is essentially enabling the R2 feature set for those with the correct licensing to do so. An upgrade for R2 won't need it since that proper licensing will be detected from the current install.
Edited by Arthur
  • Thanks 2
Posted

Since installing 2012 R2 SP1 endpoint protection isn't automatically installing on newly imaged machines. Has anyone else noticed this?

 

Thanks

Posted
Since installing 2012 R2 SP1 endpoint protection isn't automatically installing on newly imaged machines. Has anyone else noticed this?

 

Thanks

 

Ah yes I have. Although I'm only testing Win10 with my new machines so thought it might be a Win10 thing

  • 2 weeks later...
Posted

One thing I've just noticed with 2012 R2 SP1... when you're creating new OSD task sequences, pay close attention to the partition layout the task sequence puts in. The one that it created for me tried to make the main OS partition 99% of the remaining disk size after the EFI/System Reserved partitions and make the remaining 1% a system recovery partition. This was making my task sequence fail on the diskpart section.

 

Removing the recovery partition and making the main partition 100% of the remaining space fixed it for me.

  • Thanks 1
Posted
Many thanks for this tip Norphy. I was trying to deploy to VMWare Workstation and kept getting a failure during partitioning - removing the recovery partition sorted it. Interestingly, no problem deploying to Hyper-V though.
Posted
Since installing 2012 R2 SP1 endpoint protection isn't automatically installing on newly imaged machines. Has anyone else noticed this?

 

Thanks

 

Did you manage to find the problem and resolve it?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...