deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-22 18:27:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'refs/remotes/origin/master' into vs-wiprs2

Browse Source
This commit is contained in:
LizRoss 2017-03-24 14:16:38 -07:00
commit d41dd47ab8
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deploy/upgrade-readiness-get-started.md
View File

@ -44,7 +44,7 @@ If you are already using OMS, you’ll find Upgrade Readiness in the Solutions G
If you are not using OMS:
1. Go to the [Upgrade Readiness page on Microsoft.com](https://go.microsoft.com/fwlink/?LinkID=799190&clcid=0x409) and click **Sign up** to kick off the onboarding process.
1. Go to the [Upgrade Readiness page on Microsoft.com](https://go.microsoft.com/fwlink/?LinkID=799190&clcid=0x409) and click **New Customers >** to kick off the onboarding process.
2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.
3. Create a new OMS workspace. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Select **Create**.
4. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator.
@ -130,4 +130,4 @@ To ensure that user computers are receiving the most up to date data from Micros
### Distribute the deployment script at scale
Use a software distribution system such as System Center Configuration Manager to distribute the Upgrade Readiness deployment script at scale. For more information, see the [Upgrade Readiness blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/).
Use a software distribution system such as System Center Configuration Manager to distribute the Upgrade Readiness deployment script at scale. For more information, see the [Upgrade Readiness blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/).

12
windows/keep-secure/interactive-logon-prompt-user-to-change-password-before-expiration.md
View File

@ -43,10 +43,10 @@ The following table lists the actual and effective default values for this polic
| - | - |
| Default Domain Policy| Not defined|
| Default Domain Controller Policy | Not defined|
| Stand-Alone Server Default Settings | 14 days|
| DC Effective Default Settings | 14 days |
| Member Server Effective Default Settings| 14 days |
| Client Computer Effective Default Settings | 14 days|
| Stand-Alone Server Default Settings | 5 days|
| DC Effective Default Settings | 5 days |
| Member Server Effective Default Settings| 5 days |
| Client Computer Effective Default Settings | 5 days|
 
## Policy management
@ -74,11 +74,11 @@ If user passwords are configured to expire periodically in your organization, us
### Countermeasure
Configure the **Interactive logon: Prompt user to change password before expiration** setting to 14 days.
Configure the **Interactive logon: Prompt user to change password before expiration** setting to 5 days.
### Potential impact
Users see a dialog-box prompt to change their password each time that they log on to the domain when their password is configured to expire in 14 or fewer days.
Users see a dialog-box prompt to change their password each time that they log on to the domain when their password is configured to expire in 5 or fewer days.
## Related topics