Skip to content

1602 Woes

Featured Replies

Hi!

 

I upgraded my environment from 1511 to 1602.

After upgrading, application deployment during OS deployment is broken with these error: The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.

 

Supposedly there is a fix for that at http://scug.be/sccm/2013/01/27/configmgr-2012-sp1-powershell-script-to-repair-broken-applications-after-upgrading-them-from-rtm/but the site is down for me :mellow:

 

 

Also, after updating to 1602 - all my clients were no longer able to communicate with the server; 'days since communication' keeps increasing for *all* clients - even though they are all online.

I tried pushing the latest client to all PCs - the latest client installed successfully - but all the clients still fail to communicate with the server, and now all have become unmanaged :unsure:

 

Anyone had similar problems with client losing communication after upgrading to 1602? What's the best way to fix?

Thank you.

  • Author

Removing the MP role from all site servers and then re-adding it again solved both issues! Didn't need to run the script from scug.be / force a new content ID for all application deployments.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.