I am starting work on upgrading our ConfigMgr2012 R2 hierarchies to the new “Configuration Manager with no more version numbers” build 1511. There are roughly 120+ site servers in the central hierarchy (across 2 CAS hierarchies), so hopefully things go well.

I’ll keep this page to note any special gotchas that are outside the various step-by-step guides already out there, and also some easy quick link references.

Upgrade Install guides, take your pick. There are others out there, but make sure you test first in a Lab to ensure the instructions are still correct as there may have been product changes since the guides were written

 

OS

  • No specific OS related issues (yet)

SQL

  • When performing the /testdbupgrade test the database copy must be on a separate SQL instance (or SQL server) to the current site server database. i.e. don’t mount a copy of the database in the same instance
  • TBC – Stop existing SQL AG mirrors prior to upgade (we use them as read-only copies to offload reporting, not for actual Availability purposes)
  • If SQL is installed on a remote server/instance, make sure the installation account you are using has SYSADMIN permissions to the SQL instance. (Our SQL DBA’s insist on removing sysadmin rights from the account despite Microsoft stating it should be granted)

Configuration Manager

  • Windows 10 Servicing – Watch out if you start enabling the Windows 10 Servicing functions. I imagine many people will discover this “issue” when they realise they have suddenly run out of disk space! Best approach is to manually download specific Upgrades as they are identified as needed in your environment. I am testing to see if setting the evaluation schedule to “Do not run this rule automatically” is enough to stop the download. If not, then will need to “Disable” the plan To stop it downloading all the files, you need to disable the Plan completely. You can still download the “required” updates manually as needed. This is something that really needs to be improved in future updates of CM
  • TBC – Test impact of automatic Client upgrade in very large environments (150,000+ clients)

WSUS

MDT

ADK

 

 

This will be a quick reference page for links to build numbers for versions of various products

Configuration Manager 2012

Exchange 2007-2010

Exchange 2013

SQL Server

Windows Server and Workstation – Need better reference with build numbers

During the process of numerous upgrades of the OS during the Windows 10 technical preview, I’ve found quite often that my Windows Apps often stop working properly, or display as non functioning icons showing the meaningless name of the app instead of the proper app tile.

Two quick things to try to resolve:

  1. From an elevated command prompt run “wsreset”
    1. This will trigger a “Windows Store Reset” and may or may not resolve any initial problem you have opening the Store App
  2. From an elevated Powershell prompt, run the following
Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

This should re-register all the apps that appear in your app cache.

There are still many other potential issues you might encounter such as proxy servers blocking access or corrupt apps, but it’s a relatively easy starting point.

Following on from some recent database corruptions and repairs, I decided it was a good idea to create a new Exchange database and move all my mailboxes across to it.

This worked fine for all but one, which also happened to be my own.

Every time I would do the migration, it would all appear to be fine, but then it would finish as Completed, with no errors, but showing in the EAC as Synced and Finalized mailboxes: 0 of 0

I tried again and watched more closely and noticed it the extended “show details” that it was reporting an issue with the not being able to connect to the System Attendant mailbox. Various searches led me to articles about if the arbitration mailbox is accidentaly deleted how to re-create it etc, but this was not the problem.

Digging a bit further I noticed a mention of the mailbox being Quarantined.

Read the rest of this entry »

This has happened to me a couple of times in the various Technical Preview updates where the start menu stop working.

It turns out a simple powershell command will rebuild the appcache to resolve

Run this in Powershell as admin

Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanifest.xml”)}

I recently experienced an issue with a very large number of ConfigMgr 2007 package updates (400) to a large number of sites (1700). It turns out there was already a distribution job that was “stuck” in the queue and when the large update went out it resulted in a massive backlog. The end result being there were over 1.3 million files in the Replication Manager inbox that just weren’t being processed, and the number was increasing.

The only option in this sort of situation is to stop the services, move the files out of the inbox, let normal inbox processing resume and then copy the files back in a block at a time. In this case doing this manually wasn’t an option due to the number of files, so I resorted to a quick script based on the one found here: https://tricksntreats.wordpress.com/2010/05/30/sccm-backlog-fighting/

Read the rest of this entry »

A quick link reference so I don’t keep having to hunt for it in the future. Finding what the current release status is for Windows Phone updates in Australia

http://www.microsoft.com/en/mobile/support/software-update/wp8-software-update/wp8-availability-in-asia-pacific/

When trying to connect to a remote Windows 10 machine using TeamViewer, you get a blank screen with the message “The screen cannot be captured at the moment. This is probably due to fast user switching or a disconnected/minimized Remote Desktop session.”

On the computer you are trying to connect to, you may see the screen appear to flicker constantly

tv-error  Read the rest of this entry »

I first had this happen on just one of my servers. It was annoying and was causing massive numbers of WMI entries in the event logs each time it happened. I tried to just stop and disable the ConfigMgr client, but it would be “reactivated” again by something. Recently at a client site I found it happening an a large number… so time to investigate.

I checked there were no push jobs running, but there was *something* causing it to repeat. Some digging later and I finally found the reason.

There is a scheduled task created by CCMSETUP to retry if it isn’t able to install correctly on the first attempt. Under some circumstances, this task isn’t cleaned up and so the reinstall keeps happening

Read the rest of this entry »

When you need to change the location that you have been saving all your package source files, you will then need to update all the existing packages and applications to point to that new location.

(Note: See here to read what happens when you do update all your source locations)

This is fairly simple for Packages, but is a bit more complicated for Applications Read the rest of this entry »