anyweb

Introduction I was upgrading my Technical Preview 1902.2 lab to 1903TP and all went well, except for the AdminConsole upgrade (which now takes place a couple of minutes after the upgrade is done). After the site server upgrade is complete, you'll see a new notification in the AdminConsole advising you to upgrade your console. A required component of the console is out of sync with your site. Install the new console version. After clicking on Install the new console version, the Admin Console automatically closes and an MSI kicks off, a few seconds later it fails with an odd error about lack of free disk space. There is not enough available disk space on to complete this operation. Installation requires at least 20MB free disk space. I double checked my server storage and sure enough I had lots of free space, well above the 20MB mentioned. To get details of why the Admin console was failing, I referred to the ConfigMgrAdminUISetup.log and ConfigMgrAdminUISetupVerbose.log logs located in the root of C:\ The following shows the error. The error occurs in the CcmCheckFreeDiskSpace check. And interestingly it's referring to a TARGETDIR on my D:\ drive. This is the target location for the AdminConsole. Resolution Close the ConfigMgr console and any MSI installation(s) that are in progress. Using Windows File Explorer. Next, rename the AdminConsole directory as specified via the TARGETDIR line in ConfigMgrAdminUISetupVerbose.log to AdminConsole.OLD as shown below. Before changing folder name. And here's the same folder after changing it to AdminConsole.old. Once done, search the ConfigMgrAdminUISetupVerbose.log log file for the following line CURRENTDIRECTORY = C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\ Here's that line highlighted. Now that you know where the MSI installer is, browse to that folder using Windows File Explorer, answer Yes if prompted. and double click on the ConsoleSetup.exe file contained within. You will be prompted with the ConsoleSetup wizard, click your way through it to completion. And once done, you'll see the new upgraded console !

well it's out now so get upgrading

was the TPM enabled ?

Introduction In a previous set of guides you used PowerShell scripts to quickly install System Center Configuration Manager (Current Branch) version 1802 and then upgraded it using Updates and Servicing to System Center Configuration Manager (Current Branch) version 1810. Configuration Manager has a rich history that is nicely explained in the following graphic (from Twitter). Tip: You have rights to use System Center Configuration Manager (SCCM) to manage clients covered by the EMS license. Make sure you stay on #ConfigMgr current branch to receive benefits of Microsoft cloud, more info here. In case you are not already aware there are two main branches (of Configuration Manager) available: System Center Configuration Manager (Current Branch) System Center Configuration Manager (Technical Preview) System Center Configuration Manager (Current Branch) is designed for use in production environments, for managing anything from small to very large Enterprises, whereas System Center Configuration Manager (Technical Preview) is for lab testing environments only and is limited to 10 clients. The Technical Preview releases are released monthly, and contain the latest and greatest features being trialed in the product, and usually these new features are the result of feedback from uservoice. Current Branch releases on the other hand are released only a few times per year and contain stable, tested features that are mature enough to release into production environments. New baseline release Microsoft have released the latest Current Branch offering known as Update 1902 for Configuration Manager current branch so it's time to upgrade again. This release is the new baseline release (and will of course be uploaded to MSDN and VLSC soon). To understand what baseline releases are and why they are important see this post. Baseline releases media are used when doing New installs or upgrades from supported versions of SCCM. Checklist Before starting the upgrade, please verify that you have read the checklist from Microsoft here. Upgrading to 1902 When new Current Branch releases are made public, you have the choice of getting it immediately using a fast ring PowerShell script, or to wait a couple of weeks until it is made available to the slow ring (and then show up in the ConfigMgr console). To use the fast ring PowerShell script, download it, and run it to self-extract to C:\EnableFastRing1902. Once extracted, start a PowerShell cmd prompt in that folder and from there use the following command (where CM01 is the <SiteServer_Name | SiteServer_IP> of your CAS or standalone Primary site server). .\EnableFastUpdateRing1902.ps1 CM01 Tip: Some antivirus programs, particularly 3rd party (non Microsoft) antivirus programs can cause issues with the upgrade. If you have a 3rd party antivirus program installed on your site server, please disable (or temporarily uninstall) it prior to running the upgrade. To start the upgrade open the ConfigMgr console and find the Updates and servicing node as shown here. You can see that Configuration Manager 1810 Current Branch is already installed. Click on Check for Updates in the ribbon. And as instructed in the popup, open the DMPDownloader.log using CMTrace to monitor the process of checking for updates. Here you can see Generating state message: 6 which highlights that it’s found an applicable update. Once it's found if you refresh the console you'll see it listed. In the ConfigMgr console you’ll see it’s in a state of downloading or available to download, if it's not downloading yet, right click to download. Once it has completed downloading it will be listed as a state of Available. You need to click refresh in the ConfigMgr console to update the view. Installing the Update The state will change to Ready to Install once it has downloaded all the content. Right click on the update and choose Install Update Pack. when the Wizard appears, make your choice for pre-reqs and click next. Review the features included in this update pack and select those you want to use. Note: You may also notice Pre-Release features that are greyed out, to turn them on see the steps after upgrading the console the bottom of this guide. Continue through the wizard until completion at which point the update will be listed with a state of Installing. You can review the installation status by clicking on View Status. Monitor the installation At this point you can use CMTrace to open the CMUpdate.log file in <drv>\Program Files\Microsoft Configuration Manager\Logs (where drv is the drive letter you installed ConfigMgr on) to monitor the installation live. Note: The CMUpdate.log will take some time to start logging the installation of the update, so be patient if nothing appears to happen, it will. Look for a line similar to the one below to signal that the update has begun. Detected a change to the "E:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directory. Keep monitoring the CMUpdate.log file to review details of what the update is doing. Once the update is complete, you should see a hman notification in the log . Note: If you don’t see this and see an upgrade failure message then scroll up in the CMUpdate.log file to determine what the failure reason was. You can always retry an upgrade (maybe not enough available ram for example). You can also verify the status in the monitoring node or click on Show Status in Updates and Servicing. This status will continue to update in the 5 states listed: Download Replication Prerequisite Check Installation Post Installation You can click on any state to get details of what is happening at that time (tip: hit refresh). After the update is complete, click refresh in the console and you'll be reminded to update the ConfigMgr Console via a popup. Make sure to update your console as you cannot use the new features until you do. Click OK to upgrade your ConfigMgr console, and after all is done you’ll see the 1902 version listed in the console. The new version of ConfigMgr is 5.00.8790.1000. After upgrading the site Tip: If you want to gain access to the Pre-Release features, then select Sites, Hierarchy Settings, and place a checkmark in Consent to use Pre-Release features. Then go to Overview, Updates and Servicing and expand Features as shown below, you can then turn on (or off) any of the Pre-Release features you want to test in Production. Related reading What's new in System Center Configuration Manager version 1902 - https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1902 Release Notes - https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/release-notes

hi Sanjay, i just tried and both downloads work fine, they do not work for non-registered users which may have been the case for you when you tried to download them, please retry, now that you are a member cheers niall

pretty much all computers need drivers, what makes you think the Surface Pro does not ? have you tried deploying it yet ?

just make sure your Apply Driver Package step references that, as shown here.

you only need the one step, that's how it works, it's a variable !

without the accompanying smsts.log file we'd only be guessing what the issue is, if it's real hardware i'd guess that you might be missing storage drivers, attach the entire smsts.log file and we can take a look

here's a quote from the original post: Tip: If you have rendering issues with the popup on different devices then edit the call ResizeWindow(425,335,500,375) values and ResizeWindow Function in UPGRADE.HTA to fit your specific needs, I don't have access to too much hardware to test this on. The popup is fixed, if you want the user to be able to move it change the line caption="no" to caption="yes". If you want to programmatically use it then add a Window.moveTo(x, y) line. cheers niall

add a continue on error on your application install steps, then once done, attach the smsts*.log files here so we can troubleshoot.

World Backup Day is something we’re used to mark as an event every year, as a reminder we need to take good care of our data. But this year Altaro challenges us to change our mindsets and start considering the value of a good backup solution not just once, but every day. On this occasion, they’re launching this contest where you might win an Oculus Rift & Touch Virtual Reality System! Let’s hope you’ll be the lucky winner, but if not, they’re giving free eGift Amazon cards as well for all the valid entries. So, for those who want to give it a try, this seems to be a good time to do it.To enter the contest, click here. Good luck and happy backup!

first things first, i hope you snap shotted your labs after each part like i suggested at the start of these guides, secondly, if you look at step 4 part 4 here have you missed anything ? my CDP locations looks quite different to yours and don't point to the root ca at all, but instead it's on the IssuingCA, so how did you cdp end up on the rootca (if you followed my guides...)

give it a go, it doesn't look perfect but let's see how it goes

change the Upgrade Operating System step to include the %drivers01% variable, read my original blog post again from start to finish to see what you missed.

well i don't know what your apply operating system step looks like, can you show us

well you'll need to add some drivers for the chosen model, use WMI queries to determine which model it is

ok well if it's restarting over and over it's probably missing drivers, did you apply any driver package for that model during the IPU task sequence ?

I mean I scheduled updates and something broke. I checked everywhere on my primary site but i am not able to find it. Please guide me. is your post related to using an Upgrade Task Sequence in ConfigMgr or something else ? if it's something else then please raise a new topic.

how can I make this TS lightweight, what steps can be disabled from screenshots attached? you could just create a new task sequence from scratch (non MDT integrated) and start learning what each step does Do I use DISM to capture a custom image with drivers and software on it or how can I do this? I don't capture images today any more, and instead just deploy the built in install.wim (thin image) and use the task sequence steps to customize it, however some people still like to capture thick images, and for that they tend to use MDT, or even SCCM using build and capture. Is it better to include the drivers with DISM or with this TS? never include drivers in a captured image, always inject drivers using steps in the task sequence which are based on wmi queries by make/model, or use modern driver management Would it be possible to customize start menu tiles and shortcuts to my preference? absolutely, i've a blog post here on that

First of all I'd backup your SQL server db's, then move SQL server to it's own dedicated drives, one for SQL DB and another for SQL logs, once done you can try the advice here https://stackoverflow.com/questions/829542/how-do-i-decrease-the-size-of-my-sql-server-log-file

there's some info about iphelpers here

Configuring DHCP should not be necessary, but for UEFI boot where switches are involved using IPHelpers is recommended. Talk to your network guys for help with that. when you PXE boot the client computer (test with virtual machines, eg: hyperv, it's best) then what exactly do you see ? is there any error, if so what ?

ok one step at a time, what do you see when you try to PXE boot the computer, and are you testing this in a lab or in production ? did you update the boot images to the dp ? did you enable them for PXE ?

your query is incorrect SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “HP Compaq 8200 Elite SFF PC” try replacing it with this instead SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "HP Compaq 8200 Elite SFF PC" also, are you sure that the computer model is indeed HP Compaq 8200 Elite SFF PC ?