Citrix, Virtualization and Cloud

I had the problem that users of iOS devices couldn't log in to the Skype for Business Client on their devices. The reason of the problem was very simple. iOS clients doesn't support the basic NTLM authentication method. Resolution Check the web service configuration from the Skype for Business Server with the following steps: Start the Skype for Business Management Shell and view the web service settings with the command " Get-CsWebServiceConfiguation " Change the settings with the command " Set-CsWebServiceConfiguration -UseWindowsAuth Negotiate " (Default setting is NTLM) Check the new configuration with the command from Step 1 Now the iOS users can sign in again to Skype for Business Client. Good luck!

You can find the log of the task sequence on the following locations (is depending of the progress of the the task sequence): Before hard drive is formatted and partitioned X:\Windows\Temp\smstslog\smsts.log After hard drive formatted X:\smstslog\smsts.log and then copied to C:\_SMSTaskSequence\Logs\Smstslog\smsts.log Before SCCM agent installed C:\_SMSTaskSequence\Logs\Smstslog\smsts.log After SCCM agent installed %SystemRoot%\CCM\Logs\Smstslog\smsts.log After the task sequence is complete %SystemRoot%\CCM\Logs\smsts.log Good luck with the task sequence! ;-)

02.10.2015: The new version 16.0.6227.6350 has no longer this problem. Update your Office Deployment Toolkit and have fun. ;-) I ran into a issue tonight with the new Office Deployment Toolkit with support for Office 2016. The workaround is very simple, but you must first get it. :-) The bug is in version 16.0.6216.6351 of the tool. What is the problem? The Office Deployment Tool (version 16.0.6216.6351) gives the error code 30015-1007 (123) because it can not automatically detect where to save the setup files to. How to fix this issue? Create a new folder called " Office " in the same directory as setup.exe Inside this folder, you must create another folder called " Data " Inside the "Data" folder you must create a file " v32.cab " or for the 64-bit version of Office " v64.cab " (example: \Office\data\v32.cab ) Start the download again an it will works (example: setup.exe /download Download.xml ) I hope the office tea

How to eliminate slack space in the Microsoft ConfigMgr 2007 database? I have a customer with a big Microsoft Configuration Manager 2007 database (more than 25 GB). The table Policy and the ci_sdmpackages table were unusually large. I found that the disk space consumption comes from a FEP 2010 bug... I can fix this issue with the following SQL-Commands. Please make a backup of your database before you start with the execution of the commands and look for enough disk space (minimum double of database size)! Good luck! First SQL command: DELETE FROM Policy WHERE PolicyID NOT IN (SELECT PolicyID FROM PolicyAssignment WHERE PADBID IN (SELECT PADBID FROM ResPolicyMap)) AND PolicyID NOT IN (SELECT ModelName FROM CI_ConfigurationItems) AND PolicyID LIKE '%SUM_%' Second SQL command: dbcc cleantable ('(Your DB Name)','ci_sdmpackages') GO alter index CI_SDMPackages_AK on ci_sdmpackages reorganize with (lob_compaction=ON) GO alter index CI_SDMPackages_AK2

The security update KB3000483  (included in KB3004375 ) requires a group policy change to be performed in order to protect against the vulnerability described in the bulletin ( MS15-011 ). If you would like to activate now the GPO " Computer Configuration/Administrative Templates/Network/Network Provider " and you missing this setting in the console? Are you working with a domain that uses the Central Store? If so, when you're editing a group policy with the snapin, the Administrative Templates section will say "Policy definitions (ADMX files) retrieved from the central store" at the end of it. If that's the case the update includes %SystemRoot%\PolicyDefinitions\NetworkProvider.admx and %SystemRoot%\PolicyDefinitions\YOURLANGUAGE\NetworkProvider.adml files that need to be copied to the Central Store ( SYSVOL\YOURDOMAIN\Policies\PolicyDefinitions , etc.) before the editor will pick up on them. Good luck!

After an update from SCCM 2007 client to SCCM 2012 client, there is sometimes show the error "Loading Software Center returned error code 0x80041013 (-2147217389)." in Software Center. This even though the client was successfully installed. I think this error is because not all parts of the old SCCM clients have been properly removed. You can fix this issue with the following steps: Open registry Go to  HKEY_CLASSES_ROOT\CLSID\{555B0C3E-41BB-4B8A-A8AE-8A9BEE761BDF}\InProcServer32 Check the value for Default is C:\WINDOWS\CCM\ccmcisdk.dll (if not, change the value) Go to  HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{555B0C3E-41BB-4B8A-A8AE-8A9BEE761BDF}\InProcServer32 Delete the value in Default (value is C:\Windows\SysWOW64\CCM\dcmsdk.dll) You can launch the software center again and you can see the applications without the error message.