B
BlueBerries
Guest
Hi,
There are two type of Office 2013 currently happening here in our env:
1. Office 2013 that was MANUALLY installed via running the setup.exe file (without Office Customization *.MSP), AND
2. Office 2013 deployment via SCCM - with Office Customization *.MSP file
They are both volume license editions with same PRO KEY, & uses KMS client key.
What would be the best Detection Method of uninstalling MANUALLY installed Office 2013 from these computers when re-deploying it via SCCM 2012?
The different I can find at the moment between the two is the Updates folder in 1. only have a readme.txr file; Updates folder in 2. has the *.MSP files.
Please shed some lights what possible detection method could be use to automate the uninstalled of MANUALLY installed Office 2013 during the Office 2013 installation via SCCM?
Thank you
Best Regards,
Continue reading...
There are two type of Office 2013 currently happening here in our env:
1. Office 2013 that was MANUALLY installed via running the setup.exe file (without Office Customization *.MSP), AND
2. Office 2013 deployment via SCCM - with Office Customization *.MSP file
They are both volume license editions with same PRO KEY, & uses KMS client key.
What would be the best Detection Method of uninstalling MANUALLY installed Office 2013 from these computers when re-deploying it via SCCM 2012?
The different I can find at the moment between the two is the Updates folder in 1. only have a readme.txr file; Updates folder in 2. has the *.MSP files.
Please shed some lights what possible detection method could be use to automate the uninstalled of MANUALLY installed Office 2013 during the Office 2013 installation via SCCM?
Thank you
Best Regards,
Continue reading...