I am in the preliminary stages of planning my migration from ConfigMgr 2007 to 2012 when it goes on RTM release. The current deployment is a single (virtual on Hyper-V) server of 2007 R2 in mixed mode which supports a workload of ~500 clients, 40 servers and 2000 or so users. We primarily deploy software to devices, but also use SCCM for OS deployment (XP and Win 7), Windows Update and FEP 2010. I need the VDI support in 2012 among other things so this will be an immediate upgrade as soon as I can.
I have a number of questions but my most pressing is what to do about my packages which are already deployed. We deploy MS Office via software deployment, which means the path to the DP is embedded as the network install path for Office into the registries of all the clients.
This poses a problem in the "configuring Office" process when Office is first run by a user.
How do others overcome this issue when upgrading your ConfigMgr deployments, changing servers and server names in the process?
In the past I have only ever resolved this by ensuring I migrate in such a way that the server, DP and package names don't change. This won't be possible with my upgrade to 2012 unless I migrate twice, which I'd rather not do.
Should I be using the "network install paths" setting in the OCT to specify a DFS share on which my office install files are stored? If so then the ConfigMgr upgrade is presumably going to require a redeployed Office package to apply this setting to all my clients?
Thanks in advance for your assistance.