Jump to content

Recommended Posts

Posted

1802 since it was released as it fixes a bunch of bugs in the last release that were bugging me :p

 

Apart from that no real difference unless you want the new fancy bits

 

Steve

  • Thanks 1
Posted

1802 as of yesterday, had to migrate my site database first due to SQL 2012 on 2008 R2, not SQL 2017 on 2016 and all working fine.

 

Liking the new features! Client caching share for 1.

  • Thanks 1
Posted
1802 seems OK to me - just replaced my site server and have been getting SCCM up and running on a new VM over the last couple of weeks. It was nice to install from fresh a shiny new version, and seems to be working fine (as opposed to last instance that had been upgraded and upgraded over the last several years). No major problems with PXE and OSD yet - just the usual two steps forward one step back until it's all going ok :rolleyes:.
  • 1 month later...
Posted
1802 as of yesterday, had to migrate my site database first due to SQL 2012 on 2008 R2, not SQL 2017 on 2016 and all working fine.
Don't suppose you mind sharing a link on how to do this we currently run SQL 2012 so before I start on a 1802 image for the summer i want to get any prerequisites sorted. its probably obvius on the technet site but a quick serch

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...