Jump to content

Recommended Posts

Posted

Having become entirely sick of machine build times and reliability, today I noticed an option in the pre-build configuration to "retain existing Community Connect 4 packages".

 

What does this actually do in regards to outdated versions of packages etc?

 

Fearing the mighty RM CC4, my colleagues have never even dared to activate this before a build, but honestly if this speeds the process up while keeping things satisfyingly up to date, I'm willing to take the leap.

Posted

Just login to rm.com and search support for TEC2159463

 

Explanation of the 'Retain existing Community Connect 4 packages' build option

Published Date : 23 Sep 2011 Last Updated : 24 Apr 2014 Content Ref: TEC2159463

Posted

About 20 minutes to rebuild a CC4 machine if you have a restore image os SSD...although...not if you can’t boot far enough to be able to use it. Not sure why they abandoned the RMR facility with win 10.....

 

Complete new build takes around 2hours...but it depends how many packages you install. We tend to build default pc with office then deploy it...and move it to its destination in AD/RMMC where it installs the rest of the packages using BITs so it can be used while those get put on on the background...only asking to reboot if the user logs off.

 

..I just hate rembering which packages I need to do some individual for like register or enter a key code which despite my best efforts can’t automate.

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