-
Posts
9249 -
Joined
-
Last visited
-
Days Won
369
Everything posted by anyweb
-
yes, however any changes you make to the task sequence (for example adding new steps, removing steps) won't apply to any running task sequences as those computers have already download the task sequence policy (the instrucitons containing what to do in the task sequence), If you update the distribution points of any driver package that is referenced in a running task sequence then any computer that is running that task sequence may fail due to missing the content, so plan updating the content by creating v1, v2 etc driver packages and once the content is on the dp's you can switch the driver package step in the task sequence with the new version of the same (or newer) package
-
Green Field implentation ? what on earth is that ? and please tell me you are not installing SCCM on a production domain controller, have you had any training with SCCM ?
- 17 replies
-
- 1
-
-
- current branch
- sccm cb
- (and 7 more)
-
with what exactly, it's as clear as mud.
- 7 replies
-
- system center configuration manager
- sccm 2012
- (and 7 more)
-
sccm WinPE reboots at "Preparing Network Connections"
anyweb replied to Naro's topic in Configuration Manager 2012
are you sure it has the right ip address, looks to me like it's using the vmware workstation dhcp server (192.168) instead of your actual ip range (10.x.x.x) -
you can upgrade from SCCM 2012 SP2 directly to the 1702 CB baseline. In-place upgrade paths Upgrade to version 1702 When you have version 1702 baseline media, you can upgrade the following to a fully licensed version of System Center Configuration Manager version 1702: An evaluation install of System Center Configuration Manager version 1702 System Center 2012 Configuration Manager with Service Pack 1 System Center 2012 Configuration Manager with Service Pack 2 System Center 2012 R2 Configuration Manager System Center 2012 R2 Configuration Manager with Service Pack 1 Once done with the upgrade to 1702, you can upgrade the Operating System of the server.
- 17 replies
-
- current branch
- sccm cb
- (and 7 more)
-
you should not upgrade the server os until SCCM can support it, and that means SCCM needs to be at version 1602 or later When you use Configuration Manager version 1602 or later, it is also supported to upgrade Windows Server 2008 R2 to Windows Server 2012 R2 (See additional details. more details below https://docs.microsoft.com/en-us/sccm/core/servers/manage/upgrade-on-premises-infrastructure#bkmk_from2008r2 Upgrade Windows Server 2008 R2 to Windows Server 2012 R2 This operating system upgrade scenario has the following conditions: Before upgrade: Uninstall WSUS 3.2. Before you upgrade a server operating system to Windows Server 2012 R2, you must uninstall WSUS 3.2 from the server. For information about this critical step, see the New and changed functionality section in Windows Server Update Services Overview in the Windows Server documentation. After upgrade: Ensure the Windows Deployment Service is started and running for the following site system roles (this service is stopped during upgrade): Site server Management point Application Catalog web service point Application Catalog website point Ensure the Windows Process Activation and WWW/W3svc services are enabled, set for automatic start, and running for the following site system roles (these services are disabled during upgrade): Site server Management point Application Catalog web service point Application Catalog website point Ensure each server that hosts a site system role continues to meet all of perquisites for site system roles that run on that server. For example, you might need to reinstall BITS, WSUS, or configure specific settings for IIS. After restoring any missing prerequisites, restart the server one more time to ensure services are started and operational. Unsupported upgrade scenarios The following Windows Server upgrade scenarios are commonly asked about, but not supported by Configuration Manager: Windows Server 2008 to Windows Server 2012 or later Windows Server 2008 R2 to Windows Server 2012
- 17 replies
-
- current branch
- sccm cb
- (and 7 more)
-
try this, it should help https://www.niallbrady.com/2016/05/17/introducing-the-windows-10-uefi-bitlocker-frontend-for-system-center-configuration-manager-current-branch/
-
Curious I see that for the pending reboot you returned it to Exit99 I thought you said for the task sequence to kick off after the reboot it would have to be Exit0. Either way I will test and adjust. yes, i tested it some more and decided it's the best option for now, however i have some ideas to improve upon it going forward, and if i get time i'll script the, but for now this will have to do I will suggest for sanity of the end user to do the hardware check before disk space, vpn, etc. no sense having them clean up disk space, connect power or disconnect from VPN if they are then going to be told their hardware is not compatible with the upgrade. Just a thought. good point, i've modified it again so that the check if model supported is the first check, i've uploaded the modified scripts thanks.
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
ok bug found and fixed, please re-download the scripts, retest and let me know is it ok for you
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
i've changed the code order so it performs the checks like this, i'll upload the updated code shortly
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
gotcha ! thanks for posting this i'll modify the code shortly
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
good thoughts, i'll look at it and possibly reorder things, thanks for the comments check for power, vpn and disk space will endlessly prompt the end user until resolved, so that leaves hardware support, but i'll look at it again
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
the user must login, and no the wrapper won't run again, the ts should start after the user logs in, please test, verify and report any issues
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
if it exit's with 99 the ts will never start, the ts can only start if it exits with exit code 0, and as we know we are about to start the ts we clear the numberofupgradedefers reg key
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
and i've updated the main script with that fix now fyi
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
good point, fix added, here's the fix ' delete the number of deferals left, so the next forced upgrade will start with 5 deferrals KeyToDel = "NumberOfUpgradeDefers" DeleteRegKey(KeyToDel) i'll update the script with this fix shortly
- 242 replies
-
- 1702
- forced upgrade
-
(and 2 more)
Tagged with:
-
Build failures on SCCM 1710
anyweb replied to Config Mangler's topic in System Center Configuration Manager (Current Branch)
is the hardware old, have you tried upgrading the bios in the start of the task sequence on models that are failing -
Build failures on SCCM 1710
anyweb replied to Config Mangler's topic in System Center Configuration Manager (Current Branch)
new computer install or upgrade ? -
boot.sdi won't load
anyweb replied to xerxes2985's topic in System Center Configuration Manager (Current Branch)
mine is loading boot.sdi fine and even the boot wim, but it takes 20 minutes or so to load that boot wim, so it's painful -
Question about SCCM CB Alerts
anyweb replied to cylonsurfer's topic in System Center Configuration Manager (Current Branch)
according to this link the following actions are available for alerts So have your alerts state changed to cancel ? can you show a screenshot ? cheers niall -
boot.sdi won't load
anyweb replied to xerxes2985's topic in System Center Configuration Manager (Current Branch)
thanks for posting the solution ! i'm also seeing really slow network boot on some vmware workstation labs I have... it would be great to increase that speed somehow -
Choosing upgrade path
anyweb replied to Jorin's topic in System Center Configuration Manager (Current Branch)
you can upgrade directly but you'll need to be running a supported version of SQL server, the path to SCCM 1710CB is roughly as follows upgrade SQL to a supported version Upgrade SCCM 2012 R2 SP1 to SCCM 1702CB Upgrade SCCM 1702 CB to SCCM 1710CB Apply the SCCM 1710CB hotfix you can also do an inplace upgrade of server 2012r2 to server 2016 but you'll need to uninstall WSUS 3.2 first and reinstall WSUS after the upgrade -
once again, don't create a test environment in production, you'll regret it later. Get a laptop or desktop with 16GB or ram and 500GB ssd and install AD and SCCM virtual machines on that, can you not do that instead ? if you use the production environment to do your test environment then all i can say is read what i said above cheers niall
- 17 replies
-
- current branch
- sccm cb
- (and 7 more)
