If you start using the Application Catalog from Configuration Manager 2012 R2 SP1 you have to configure some settings before the users can access it.
Probably you recieve a login propt when accessing the application catalog from your client.
After installing the role and checking the logs for a successfull installtion (SMSAWEBSVCSetup.log & SMSPORTALWEBSetup.log) you have to change the client settings:
- Change the “Computer Agent” settings:
- Select your Application Catalog website:
- Add your Application Catalog website to your clients by using Group Policy:
This steps will allow you to use the Application Catalog without any logon prompts. Configure also your Enterprise Mode settings when you use Windows 10 EDGE Browser. EDGE does not support Silverlight but the Software Center and the Application Catalog is using Silverlight.
After blogging on sccmfaq.ch I finally started my own blog – blog.alschneiter.com. I’m focused on all the new and rising Microsoft Windows Client technologies. This includes stuff like, Windows 10, Configuration Manager (ConfigMgr), EMS, Office365, Azure RemoteApps, Remote Desktop Services (RDS), MDOP and much more! Just the modern workplace. Any questions to me? Feel free to contact me using this blog or twitter!
And, don’t miss all the technical deep dives, technical news and also some fun stuff. Subscribe right now!
In some cases (DNS changes, expired certificate, etc.) you have to renew a certificate on your RD Webservers. I hat to do this today on a environment wit two RD Web Servers load balanced by a F5 Loadbalancer. But just replacing the web certificate on the RD Connection broker was not enough.
For some reason the cert was not valid after the replacement.
- Delete all the old certificates in the personal store of the RD Webservers
- Reboot the Webservers
- Request a new certificate by using certlm.msc of one of the RD Webservers
- Export the .pfx file for the Connection Broker
- Redeploy the certificate using the Server Manger / Remote Desktop Services / Deployment Overview / Tasks / Edit Deployment Settings
This should allow you to access the RD Websites without having any certificates warnings.
Today I had to deploy Skype for Business for a Office 365 Business Premium Plan using ConfigMgr 2012 R2. This is a special O365 plan for a maximum of 300 users.
Normally with an E3 plan you can use a config.XML file with the lync product code entry called “LyncRetail”.
This is not working for all other plans like E1, E2, Business, BusinessPremium etc.! You have to change the product code to “LyncEntryRetail” otherwise you won’t be able to activate your Skype for Business installation.
This is how my config file now looks like:
<Language ID=”en-us” />
<Language ID=”en-us” />
<Update Enabled=”TRUE” />
<Display Level=”None” AcceptEULA=”TRUE” />
<Logging Name=”OfficeSetup.txt” Path=”%temp%” />
Here you can find a list of all supported products: https://support.microsoft.com/en-us/kb/2842297
Maybe this helps.
One of our customer had an issue with the ADFS farm running on Windows Server 2012 R2. There was a problem with the ADFS proxy which was domain joined. This is not a recommended configuration so we changed that to a workgroup machine.
The https://adfs.DOMAIN.COM/adfs/ls/IdpInitiatedSignon.aspx could be contacted after that and a Login was possible. Hovever, an enrollemnt of devices using Microsoft Intune was still not working. We recoginized that the realying trust to Office 365 was missing on the ADFS Server:
Using powershell to create the trust worked but didn’t allow the user to Login to https://account.manage.microsoft.com or the comany portal and enroll devices.
Connect-MsolService –Credential $cred
Set-MsolAdfscontext -Computer “FQDN of Server”
Convert-MsolDomainToFederated –DomainName “Your Domain Name”
The error 8004789A occured on the Login page.
You have to use the powershell command
Update-MsolFederatedDomain –DomainName “Your Domain Name”
This did the trick.
Maybe this helps someone.