Skip to main content

Posts

Showing posts from October, 2015

SCCM 2012 Troubleshooting

Client-side logging By default, the client-side logging level is set to the value 1 in the registry. This means that Configuration Manager logs only Information, Warning, and Error messages. To enable verbose logging for those Configuration Manager logs that support it, do the following: 1. Open Registry Editor and find: HKLM\Software\Microsoft\CCM\Logging\@GLOBAL\LogLevel 2. Change the value of LogLevel from 1 to 0 (note that you will need to change the permissions for Administrators to have Full Control in order to change this value). 3. Restart the SMS Agent Host service. Client-side debug logging For even greater detail, you can enable debug logging. To enable debug logging for Configuration Manager logs, do the following: 1. Open Registry Editor and find: HKLM\Software\Microsoft\CC\Logging 2. Create a new key called DebugLogging. 3. Create a new value of type REG_SZ under this key and name it Enabled. 4. Set the Enabled value to True. 5. Restart the SMS Agent Host service.

SCCM 2012 Troubleshooting

Client-side logging By default, the client-side logging level is set to the value 1 in the registry. This means that Configuration Manager logs only Information, Warning, and Error messages. To enable verbose logging for those Configuration Manager logs that support it, do the following: 1. Open Registry Editor and find: HKLM\Software\Microsoft\CCM\Logging\@GLOBAL\LogLevel 2. Change the value of LogLevel from 1 to 0 (note that you will need to change the permissions for Administrators to have Full Control in order to change this value). 3. Restart the SMS Agent Host service. Client-side debug logging For even greater detail, you can enable debug logging. To enable debug logging for Configuration Manager logs, do the following: 1. Open Registry Editor and find: HKLM\Software\Microsoft\CC\Logging 2. Create a new key called DebugLogging. 3. Create a new value of type REG_SZ under this key and name it Enabled. 4. Set the Enabled value to True. 5. Restart the SMS Agent

Office 365 upgrade from office 2007, 2010, and 2013

Office 365 upgrade from Office 2007, 2010, 2013, 2016 Scenario : Estate contains Office Professional Plus and Standard installations of 2007, 2010, 2013 and 2016.  All version of Office suites must be removed leaving Visio and Project installation alone (i.e. 2007,2010, 2013, and 2016). The source files for Office 365 can be downloaded via the Click-To-Run URL here . This will download and extract two files (setup.exe and Configuration.xml). A download.xml and install.xml can be extrapolated from the accompanied configuration.xml; see below. “The Office 2016 Deployment Tool allows the administrator to customize and manage Office 2016 Click-to-Run deployments. This tool will help administrators to manage installations sources, product/language combinations, and deployment configuration options for Office Click-to-Run.” http://www.microsoft.com/en-us/download/details.aspx?id=36778 1.1        Download.xml The download.xml within the source files is kept as reference but is no longer requ