mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 14:57:23 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into wsfb-9502045
This commit is contained in:
Trudy Hakala
commit
e6169d29c3
@ -109,7 +109,7 @@ Review the following information before you start the upgrade:
|
||||
<td align="left"><p>You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V 5.0 SP3.</p>
|
||||
<p>For more information, see:</p>
|
||||
<ul>
|
||||
<li><p>[About App-V 5.0](about-app-v-50.md#bkmk-diff-46-50)</p></li>
|
||||
<li><p>[About App-V 5.0](about-app-v-50.md) </p></li>
|
||||
<li><p>[Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)</p></li>
|
||||
</ul>
|
||||
<p></p></td>
|
||||
|
||||
@ -157,7 +157,6 @@ Complete the following steps to create an Office 2013 package for App-V 5.0 or l
|
||||
**Important**
|
||||
In App-V 5.0 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
|
||||
|
||||
|
||||
|
||||
### Review prerequisites for using the Office Deployment Tool
|
||||
|
||||
@ -189,11 +188,9 @@ The computer on which you are installing the Office Deployment Tool must have:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Note**
|
||||
In this topic, the term “Office 2013 App-V package” refers to subscription licensing and volume licensing.
|
||||
|
||||
|
||||
|
||||
### Create Office 2013 App-V Packages Using Office Deployment Tool
|
||||
@ -242,8 +239,6 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
**Note**
|
||||
The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file.
|
||||
|
||||
|
||||
|
||||
The above XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
|
||||
|
||||
<table>
|
||||
@ -300,8 +295,6 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2013 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
|
||||
|
||||
2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2013 applications that will later be converted into an App-V package. Below is an example command with description of details:
|
||||
@ -811,7 +804,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
<tr class="odd">
|
||||
<td align="left"><p>How do I package and publish Visio 2013 and Project 2013 with Office?</p></td>
|
||||
<td align="left"><p>You must include Visio 2013 and Project 2013 in the same package with Office.</p>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](../solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions.md).</p></td>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow [Deploying Microsoft Office 2010 by Using App-V](../appv-v5/deploying-microsoft-office-2010-by-using-app-v.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>How can I deploy Visio 2013 and Project 2013 to specific users?</p></td>
|
||||
|
||||
@ -62,7 +62,6 @@ Use the following table to get information about supported versions of Office an
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-pkg-pub-reqs"></a>Packaging, publishing, and deployment requirements
|
||||
|
||||
Before you deploy Office by using App-V, review the following requirements.
|
||||
@ -811,7 +810,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
<tr class="odd">
|
||||
<td align="left"><p>How do I package and publish Visio 2013 and Project 2013 with Office?</p></td>
|
||||
<td align="left"><p>You must include Visio 2013 and Project 2013 in the same package with Office.</p>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](../solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions.md).</p></td>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow [Deploying Microsoft Office 2010 by Using App-V](../appv-v5/deploying-microsoft-office-2010-by-using-app-v.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>How can I deploy Visio 2013 and Project 2013 to specific users?</p></td>
|
||||
|
||||
@ -88,12 +88,12 @@ Review the following requirements for using the App-V PowerShell cmdlets:
|
||||
<td align="left"><p>Run the <strong>Set-AppvClientConfiguration</strong> cmdlet with the <strong>-RequirePublishAsAdmin</strong> parameter.</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>[How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell.md#bkmk-admin-only-posh-topic-cg)</p></li>
|
||||
<li><p>[How to Manage App-V 5.0 Packages Running on a Stand-Alone Computer by Using PowerShell](how-to-manage-app-v-50-packages-running-on-a-stand-alone-computer-by-using-powershell.md#bkmk-admins-pub-pkgs)</p></li>
|
||||
<li><p>[How to Manage App-V 5.0 Packages Running on a Stand-Alone Computer by Using PowerShell](how-to-manage-app-v-50-packages-running-on-a-stand-alone-computer-by-using-powershell.md)</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Enable the “Require publish as administrator” Group Policy setting for App-V Clients.</p></td>
|
||||
<td align="left"><p>[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md#bkmk-admin-pub-pkg-only-posh)</p></td>
|
||||
<td align="left"><p>[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md) </p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -105,8 +105,6 @@ Review the following requirements for using the App-V PowerShell cmdlets:
|
||||
|
||||
|
||||
## <a href="" id="bkmk-load-cmdlets"></a>Loading the PowerShell cmdlets
|
||||
|
||||
|
||||
To load the PowerShell cmdlet modules:
|
||||
|
||||
1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
|
||||
@ -143,8 +141,6 @@ To load the PowerShell cmdlet modules:
|
||||
|
||||
|
||||
## <a href="" id="bkmk-get-cmdlet-help"></a>Getting help for the PowerShell cmdlets
|
||||
|
||||
|
||||
Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
|
||||
|
||||
<table>
|
||||
@ -204,15 +200,13 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
|
||||
|
||||
|
||||
## <a href="" id="bkmk-display-help-cmdlet"></a>Displaying the help for a PowerShell cmdlet
|
||||
|
||||
|
||||
To display help for a specific PowerShell cmdlet:
|
||||
|
||||
1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
|
||||
|
||||
2. Type **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue**? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
|
||||
|
||||
|
||||
@ -88,12 +88,12 @@ Review the following requirements for using the App-V PowerShell cmdlets:
|
||||
<td align="left"><p>Run the <strong>Set-AppvClientConfiguration</strong> cmdlet with the <strong>-RequirePublishAsAdmin</strong> parameter.</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>[How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell51.md#bkmk-admin-only-posh-topic-cg)</p></li>
|
||||
<li><p>[How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](how-to-manage-app-v-51-packages-running-on-a-stand-alone-computer-by-using-powershell.md#bkmk-admins-pub-pkgs)</p></li>
|
||||
<li><p>[How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](how-to-manage-app-v-51-packages-running-on-a-stand-alone-computer-by-using-powershell.md)</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Enable the “Require publish as administrator” Group Policy setting for App-V Clients.</p></td>
|
||||
<td align="left"><p>[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-51.md#bkmk-admin-pub-pkg-only-posh)</p></td>
|
||||
<td align="left"><p>[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-51.md)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -106,7 +106,6 @@ Review the following requirements for using the App-V PowerShell cmdlets:
|
||||
|
||||
## <a href="" id="bkmk-load-cmdlets"></a>Loading the PowerShell cmdlets
|
||||
|
||||
|
||||
To load the PowerShell cmdlet modules:
|
||||
|
||||
1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
|
||||
@ -140,11 +139,7 @@ To load the PowerShell cmdlet modules:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-get-cmdlet-help"></a>Getting help for the PowerShell cmdlets
|
||||
|
||||
|
||||
Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
|
||||
|
||||
<table>
|
||||
@ -201,11 +196,7 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-display-help-cmdlet"></a>Displaying the help for a PowerShell cmdlet
|
||||
|
||||
|
||||
To display help for a specific PowerShell cmdlet:
|
||||
|
||||
1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
|
||||
|
||||
@ -103,7 +103,7 @@ Create the following accounts for the Reports feature.
|
||||
|
||||
|
||||
|
||||
<a href="" id="bkmk-helpdesk-roles"></a>## Administration and Monitoring Website (Help Desk) accounts
|
||||
## <a href="" id="bkmk-helpdesk-roles"></a>Administration and Monitoring Website (Help Desk) accounts
|
||||
|
||||
|
||||
Create the following accounts for the Administration and Monitoring Website.
|
||||
|
||||
@ -66,7 +66,7 @@ Windows PowerShell Help for MBAM cmdlets is available in the following formats:
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>At a Windows PowerShell command prompt, type <strong>Get-Help</strong> <<em>cmdlet</em>></p></td>
|
||||
<td align="left"><p>To upload the latest Windows PowerShell cmdlets, follow the instructions in [Configuring MBAM 2.5 Server Features by Using Windows PowerShell](configuring-mbam-25-server-features-by-using-windows-powershell.md#bkmk-load-posh-help)</p></td>
|
||||
<td align="left"><p>To upload the latest Windows PowerShell cmdlets, follow the instructions in [Configuring MBAM 2.5 Server Features by Using Windows PowerShell](configuring-mbam-25-server-features-by-using-windows-powershell.md)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>On TechNet as webpages</p></td>
|
||||
|
||||
@ -191,7 +191,7 @@ The UE-V template baseline is created using the UevTemplateBaselineGenerator.exe
|
||||
|
||||
The result is a baseline CAB file that is ready for import into Configuration Manager. If at a future date, you update or add a template, you can rerun the command using the same baseline name. Importing the CAB results in CI version updates on the changed templates.
|
||||
|
||||
<a href="" id="create2"></a>### Create the First UE-V Template Baseline
|
||||
### <a href="" id="create2"></a>Create the First UE-V Template Baseline
|
||||
|
||||
1. Create a “master” set of UE-V templates in a stable folder location visible to the machine running your ConfigMgr Admin Console. As templates are added or updated, this folder is where they are pulled for distribution. The initial list of templates can be copied from a machine with UE-V installed. The default template location is C:\\Program Files\\Microsoft User Experience Virtualization\\Templates.
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ The following sections and procedures are provided in this guide:
|
||||
- [Log entry structure](#log-entry-structure): The format of a log entry is described.
|
||||
- [Analyze log files](#analyze-log-files): General procedures for log file analysis, and an example.
|
||||
- [Resolution procedures](#resolution-procedures): Causes and mitigation procedures associated with specific error codes.
|
||||
- [0xC1900101](#0xC1900101): Information about the 0xC1900101 result code.
|
||||
- [0xC1900101](#0xc1900101): Information about the 0xC1900101 result code.
|
||||
- [0x800xxxxx](#0x800xxxxx): Information about result codes that start with 0x800.
|
||||
- [Other result codes](#other-result-codes): Additional causes and mitigation procedures are provided for some result codes.
|
||||
- [Other error codes](#other-error-codes): Additional causes and mitigation procedures are provided for some error codes.
|
||||
@ -866,7 +866,7 @@ Alternatively, re-create installation media the [Media Creation Tool](https://ww
|
||||
<TD>[Analyze log files](#analyze-log-files) to determine the issue.</TD></TR>
|
||||
<TR><TD>0xC1900101 - 0x4001E
|
||||
<TD>Installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.
|
||||
<TD>This is a generic error that occurs during the OOBE phase of setup. See the [0xC1900101](#0xC1900101) section of this guide and review general troubleshooting procedures described in that section.</TD></TR>
|
||||
<TD>This is a generic error that occurs during the OOBE phase of setup. See the [0xC1900101](#0xc1900101) section of this guide and review general troubleshooting procedures described in that section.</TD></TR>
|
||||
<TR><TD>0x80070005 - 0x4000D
|
||||
<TD>The installation failed in the SECOND_BOOT phase with an error in during MIGRATE_DATA operation. This error indicates that access was denied while attempting to migrate data.
|
||||
<TD>[Analyze log files](#analyze-log-files) to determine the data point that is reporting access denied.</TD></TR>
|
||||
|
||||
@ -23,7 +23,7 @@ This topic provides a summary of available upgrade paths to Windows 10. You can
|
||||
|
||||
>**Windows N/KN**: Windows "N" and "KN" editions follow the same upgrade paths shown below. If the pre-upgrade and post-upgrade editions are not the same type (e.g. Windows 8.1 Pro N to Windows 10 Pro), personal data will be kept but applications and settings will be removed during the upgrade process.
|
||||
|
||||
>**Free upgrade**: The Windows 10 free upgrade offer expired on July 29, 2016. For more information, see [Free upgrade paths](#Free-upgrade-paths).
|
||||
>**Free upgrade**: The Windows 10 free upgrade offer expired on July 29, 2016. For more information, see [Free upgrade paths](#free-upgrade-paths).
|
||||
|
||||
✔ = Full upgrade is supported including personal data, settings, and applications.<BR>
|
||||
D = Edition downgrade; personal data is maintained, applications and settings are removed.
|
||||
|
||||
@ -25,7 +25,7 @@ To complete these procedures, you must be a member of the Domain Administrators
|
||||
|
||||
In this topic:
|
||||
|
||||
- [Add the test devices to the GPO membership groups](#to-add-test-devices-to-the-gpo-membership-group)
|
||||
- [Add the test devices to the GPO membership groups](#to-add-test-devices-to-the-gpo-membership-groups)
|
||||
|
||||
- [Refresh Group Policy on the devices in each membership group](#to-refresh-group-policy-on-a-device)
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ You can access these audit policy settings through the Local Security Policy sna
|
||||
These advanced audit policy settings allow you to select only the behaviors that you want to monitor. You can exclude audit results for behaviors that are of little or no concern to you, or behaviors that create an excessive number of log entries. In addition, because security audit policies can be applied by using domain Group Policy Objects, audit policy settings can be modified, tested, and deployed to selected users and groups with relative simplicity.
|
||||
Audit policy settings under **Security Settings\\Advanced Audit Policy Configuration** are available in the following categories:
|
||||
|
||||
**Account Logon**
|
||||
## Account Logon
|
||||
|
||||
Configuring policy settings in this category can help you document attempts to authenticate account data on a domain controller or on a local Security Accounts Manager (SAM). Unlike Logon and Logoff policy settings and events, which track attempts to access a particular computer, settings and events in this category focus on the account database that is used. This category includes the following subcategories:
|
||||
|
||||
@ -36,7 +36,7 @@ Configuring policy settings in this category can help you document attempts to a
|
||||
- [Audit Kerberos Service Ticket Operations](audit-kerberos-service-ticket-operations.md)
|
||||
- [Audit Other Logon/Logoff Events](audit-other-logonlogoff-events.md)
|
||||
|
||||
**Account Management**
|
||||
## Account Management
|
||||
|
||||
The security audit policy settings in this category can be used to monitor changes to user and computer accounts and groups. This category includes the following subcategories:
|
||||
|
||||
@ -47,7 +47,7 @@ The security audit policy settings in this category can be used to monitor chang
|
||||
- [Audit Security Group Management](audit-security-group-management.md)
|
||||
- [Audit User Account Management](audit-user-account-management.md)
|
||||
|
||||
**Detailed Tracking**
|
||||
## Detailed Tracking
|
||||
|
||||
Detailed Tracking security policy settings and audit events can be used to monitor the activities of individual applications and users on that computer, and to understand how a computer is being used. This category includes the following subcategories:
|
||||
|
||||
@ -57,7 +57,7 @@ Detailed Tracking security policy settings and audit events can be used to monit
|
||||
- [Audit Process Termination](audit-process-termination.md)
|
||||
- [Audit RPC Events](audit-rpc-events.md)
|
||||
|
||||
**DS Access**
|
||||
## DS Access
|
||||
|
||||
DS Access security audit policy settings provide a detailed audit trail of attempts to access and modify objects in Active Directory Domain Services (AD DS). These audit events are logged only on domain controllers. This category includes the following subcategories:
|
||||
|
||||
@ -66,7 +66,7 @@ DS Access security audit policy settings provide a detailed audit trail of attem
|
||||
- [Audit Directory Service Changes](audit-directory-service-changes.md)
|
||||
- [Audit Directory Service Replication](audit-directory-service-replication.md)
|
||||
|
||||
**Logon/Logoff**
|
||||
## Logon/Logoff
|
||||
|
||||
Logon/Logoff security policy settings and audit events allow you to track attempts to log on to a computer interactively or over a network. These events are particularly useful for tracking user activity and identifying potential attacks on network resources. This category includes the following subcategories:
|
||||
|
||||
@ -82,11 +82,11 @@ Logon/Logoff security policy settings and audit events allow you to track attemp
|
||||
- [Audit Other Logon/Logoff Events](audit-other-logonlogoff-events.md)
|
||||
- [Audit Special Logon](audit-special-logon.md)
|
||||
|
||||
**Object Access**
|
||||
## Object Access
|
||||
|
||||
Object Access policy settings and audit events allow you to track attempts to access specific objects or types of objects on a network or computer. To audit attempts to access a file, directory, registry key, or any other object, you must enable the appropriate object Aaccess auditing subcategory for success and/or failure events. For example, the file system subcategory needs to be enabled to audit file operations, and the Registry subcategory needs to be enabled to audit registry accesses.
|
||||
|
||||
Proving that these audit policies are in effect to an external auditor is more difficult. There is no easy way to verify that the proper SACLs are set on all inherited objects. To address this issue, see [Global Object Access Auditing](#global-object-access).
|
||||
Proving that these audit policies are in effect to an external auditor is more difficult. There is no easy way to verify that the proper SACLs are set on all inherited objects. To address this issue, see [Global Object Access Auditing](#global-object-access-auditing).
|
||||
|
||||
This category includes the following subcategories:
|
||||
|
||||
@ -105,7 +105,7 @@ This category includes the following subcategories:
|
||||
- [Audit SAM](audit-sam.md)
|
||||
- [Audit Central Access Policy Staging](audit-central-access-policy-staging.md)
|
||||
|
||||
**Policy Change**
|
||||
## Policy Change
|
||||
|
||||
Policy Change audit events allow you to track changes to important security policies on a local system or network. Because policies are typically established by administrators to help secure network resources, monitoring changes or attempts to change these policies can be an important aspect of security management for a network. This category includes the following subcategories:
|
||||
|
||||
@ -116,7 +116,7 @@ Policy Change audit events allow you to track changes to important security poli
|
||||
- [Audit MPSSVC Rule-Level Policy Change](audit-mpssvc-rule-level-policy-change.md)
|
||||
- [Audit Other Policy Change Events](audit-other-policy-change-events.md)
|
||||
|
||||
**Privilege Use**
|
||||
## Privilege Use
|
||||
|
||||
Permissions on a network are granted for users or computers to complete defined tasks. Privilege Use security policy settings and audit events allow you to track the use of certain permissions on one or more systems. This category includes the following subcategories:
|
||||
|
||||
@ -124,7 +124,7 @@ Permissions on a network are granted for users or computers to complete defined
|
||||
- [Audit Sensitive Privilege Use](audit-sensitive-privilege-use.md)
|
||||
- [Audit Other Privilege Use Events](audit-other-privilege-use-events.md)
|
||||
|
||||
**System**
|
||||
## System
|
||||
|
||||
System security policy settings and audit events allow you to track system-level changes to a computer that are not included in other categories and that have potential security implications. This category includes the following subcategories:
|
||||
|
||||
@ -134,7 +134,7 @@ System security policy settings and audit events allow you to track system-level
|
||||
- [Audit Security System Extension](audit-security-system-extension.md)
|
||||
- [Audit System Integrity](audit-system-integrity.md)
|
||||
|
||||
**Global Object Access**
|
||||
## Global Object Access Auditing
|
||||
|
||||
Global Object Access Auditing policy settings allow administrators to define computer system access control lists (SACLs) per object type for the file system or for the registry. The specified SACL is then automatically applied to every object of that type.
|
||||
Auditors will be able to prove that every resource in the system is protected by an audit policy by viewing the contents of the Global Object Access Auditing policy settings. For example, if auditors see a policy setting called "Track all changes made by group administrators," they know that this policy is in effect.
|
||||
|
||||
@ -82,7 +82,7 @@ This URL will match that seen in the Firewall or network activity.</td>
|
||||
<td>Windows Defender Advanced Threat Protection service failed to connect to the server at ```variable```.</td>
|
||||
<td>Variable = URL of the Windows Defender ATP processing servers.<br>
|
||||
The service could not contact the external processing servers at that URL.</td>
|
||||
<td>Check the connection to the URL. See [Configure proxy and Internet connectivity](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#configure-proxy-and-Internet-connectivity).</td>
|
||||
<td>Check the connection to the URL. See [Configure proxy and Internet connectivity](configure-proxy-internet-windows-defender-advanced-threat-protection.md).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>6</td>
|
||||
@ -145,7 +145,7 @@ It may take several hours for the endpoint to appear in the portal.</td>
|
||||
<td>Windows Defender Advanced Threat Protection cannot start command channel with URL: ```variable```.</td>
|
||||
<td>Variable = URL of the Windows Defender ATP processing servers.<br>
|
||||
The service could not contact the external processing servers at that URL.</td>
|
||||
<td>Check the connection to the URL. See [Configure proxy and Internet connectivity](#configure-proxy-and-Internet-connectivity).</td>
|
||||
<td>Check the connection to the URL. See [Configure proxy and Internet connectivity](configure-proxy-internet-windows-defender-advanced-threat-protection.md).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>17</td>
|
||||
|
||||
@ -81,7 +81,7 @@ Investigate the details of an alert raised on a specific machine to identify oth
|
||||
|
||||
You can click on affected machines whenever you see them in the portal to open a detailed report about that machine. Affected machines are identified in the following areas:
|
||||
|
||||
- The [Machines view](#Investigate-machines-in-the-Windows-Defender-ATP-Machines-view)
|
||||
- The [Machines view](investigate-machines-windows-defender-advanced-threat-protection.md)
|
||||
- The [Alerts queue](alerts-queue-windows-defender-advanced-threat-protection.md)
|
||||
- The [Dashboard](dashboard-windows-defender-advanced-threat-protection.md)
|
||||
- Any individual alert
|
||||
|
||||
@ -81,7 +81,7 @@ The default Administrator account is initially installed differently for Windows
|
||||
|
||||
In summary, for Windows Server operating systems, the Administrator account is used to set up the local server only for tasks that require administrative rights. The default Administrator account is set up by using the default settings that are provided on installation. Initially, the Administrator account is not associated with a password. After installation, when you first set up Windows Server, your first task is to set up the Administrator account properties securely. This includes creating a strong password and securing the **Remote control** and **Remote Desktop Services Profile** settings. You can also disable the Administrator account when it is not required.
|
||||
|
||||
In comparison, for the Windows client operating systems, the Administrator account has access to the local system only. The default Administrator account is initially disabled by default, and this account is not associated with a password. It is a best practice to leave the Administrator account disabled. The default Administrator account is considered only as a setup and disaster recovery account, and it can be used to join the computer to a domain. When administrator access is required, do not sign in as an administrator. You can sign in to your computer with your local (non-administrator) credentials and use **Run as administrator**. For more information, see [Security considerations](#security-considerations).
|
||||
In comparison, for the Windows client operating systems, the Administrator account has access to the local system only. The default Administrator account is initially disabled by default, and this account is not associated with a password. It is a best practice to leave the Administrator account disabled. The default Administrator account is considered only as a setup and disaster recovery account, and it can be used to join the computer to a domain. When administrator access is required, do not sign in as an administrator. You can sign in to your computer with your local (non-administrator) credentials and use **Run as administrator**.
|
||||
|
||||
**Account group membership**
|
||||
|
||||
|
||||
@ -30,8 +30,8 @@ The TPM Services Group Policy settings are located at:
|
||||
| [Ignore the local list of blocked TPM commands](#bkmk-tpmgp-illb) | X| X| X| X| X| X|
|
||||
| [Configure the level of TPM owner authorization information available to the operating system](#bkmk-tpmgp-oauthos)| | X| X| X|||
|
||||
| [Standard User Lockout Duration](#bkmk-tpmgp-suld)| X| X| X| X|||
|
||||
| [Standard User Individual Lockout Threshold](#individual)| X| X| X| X|||
|
||||
| [Standard User Total Lockout Threshold](#bkmk-tpmgpsutlt)| X| X| X| X||||
|
||||
| [Standard User Individual Lockout Threshold](#bkmk-individual)| X| X| X| X|||
|
||||
| [Standard User Total Lockout Threshold](#bkmk-total)| X| X| X| X||||
|
||||
|
||||
### <a href="" id="bkmk-tpmgp-addsbu"></a>Turn on TPM backup to Active Directory Domain Services
|
||||
|
||||
|
||||
@ -80,7 +80,7 @@ Set-AppvClientConfiguration -SharedContentStoreMode 1
|
||||
|
||||
The Sequencer is a tool that is used to convert standard applications into virtual packages for deployment to computers that run the App-V client. The Sequencer helps provide a simple and predictable conversion process with minimal changes to prior sequencing workflows. In addition, the Sequencer allows users to more easily configure applications to enable connections of virtualized applications.
|
||||
|
||||
For a list of changes in the App-V Sequencer, see [What's new in App-V](appv-about-appv.md#bkmk-seqimprove).
|
||||
For a list of changes in the App-V Sequencer, see [What's new in App-V](appv-about-appv.md).
|
||||
|
||||
To deploy the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
|
||||
@ -75,9 +75,9 @@ Review the following requirements for using the Windows PowerShell cmdlets:
|
||||
<p>To configure these cmdlets to require an elevated command prompt, use one of the following methods:</p>
|
||||
<ul>
|
||||
<li><p>Run the <strong>Set-AppvClientConfiguration</strong> cmdlet with the <strong>-RequirePublishAsAdmin</strong> parameter.</p>
|
||||
<p>For more information, see:<br>[How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md#bkmk-admin-only-posh-topic-cg)<br>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).</p></li>
|
||||
<p>For more information, see:<br>[How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)<br>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).</p></li>
|
||||
<li><p>Enable the “Require publish as administrator” Group Policy setting for App-V Clients.</p>
|
||||
<p>For more information, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md#bkmk-admin-pub-pkg-only-posh)</p></li>
|
||||
<p>For more information, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md)</p></li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@ -21,7 +21,7 @@ Before you can use App-V, you must install the App-V Sequencer, enable the App-V
|
||||
App-V uses a process called sequencing to create virtualized applications and application packages. Sequencing requires the use of a computer that runs the App-V Sequencer.
|
||||
|
||||
> [!NOTE]
|
||||
> For information about the new functionality of App-V sequencer, see [What's new in App-V](appv-about-appv.md#bkmk-seqimprove).
|
||||
> For information about the new functionality of App-V sequencer, see [What's new in App-V](appv-about-appv.md).
|
||||
|
||||
|
||||
The computer that runs the App-V sequencer must meet the minimum system requirements. For a list of these requirements, see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
@ -246,4 +246,4 @@ Add or vote on suggestions on the [User Experience Virtualization feedback site]
|
||||
|
||||
[Administering UE-V](uev-administering-uev.md)
|
||||
|
||||
[Deploy UE-V for Custom Applications](uev-deploy-uev-for-custom-applications.md#deploycatalogue)
|
||||
[Deploy UE-V for Custom Applications](uev-deploy-uev-for-custom-applications.md)
|
||||
@ -171,7 +171,7 @@ It might be necessary to change the PowerShell execution policy to allow these s
|
||||
|
||||
3. Reimport the CAB file. The version in ConfigMgr will be updated.
|
||||
|
||||
<a href="" id="create2"></a>## Generate a UE-V Template Baseline
|
||||
## <a href="" id="create2"></a>Generate a UE-V Template Baseline
|
||||
|
||||
UE-V templates are distributed using a baseline containing multiple configuration items. Each configuration item contains the discovery and remediation scripts needed to install one UE-V template. The actual UE-V template is embedded within the remediation script for distribution using standard Configuration Item functionality.
|
||||
|
||||
|
||||
@ -54,7 +54,7 @@ Use these UE-V components to create and manage custom templates for your third-p
|
||||
| Component | Description |
|
||||
|-------------------------------|---------------|
|
||||
| **UE-V template generator** | Use the **UE-V template generator** to create custom settings location templates that you can then distribute to user computers. The UE-V template generator also lets you edit an existing template or validate a template that was created with a different XML editor. <br>With the Windows 10, version 1607 release, the UE-V template generator is installed with the [Windows Assessment and Deployment kit for Windows 10, version 1607](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) (Windows ADK). <br>If you are upgrading from an existing UE-V installation, you’ll need to use the new generator to create new settings location templates. Application templates created with previous versions of the UE-V template generator are still supported, however. |
|
||||
| **Settings template catalog** | The **settings template catalog** is a folder path on UE-V computers or a Server Message Block (SMB) network share that stores the custom settings location templates. The UE-V service checks this location once a day, retrieves new or updated templates, and updates its synchronization behavior.<br>If you use only the UE-V default settings location templates, then a settings template catalog is unnecessary. For more information about settings deployment catalogs, see [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md#deploycatalogue). |
|
||||
| **Settings template catalog** | The **settings template catalog** is a folder path on UE-V computers or a Server Message Block (SMB) network share that stores the custom settings location templates. The UE-V service checks this location once a day, retrieves new or updated templates, and updates its synchronization behavior.<br>If you use only the UE-V default settings location templates, then a settings template catalog is unnecessary. For more information about settings deployment catalogs, see [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md).|
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE - NOTE THAT UPDATED IMAGE IS A PNG FILE
|
||||
<img src="media/image2.gif" width="595" height="330" />
|
||||
@ -64,7 +64,7 @@ Use these UE-V components to create and manage custom templates for your third-p
|
||||
|
||||
## Settings synchronized by default
|
||||
|
||||
UE-V synchronizes settings for these applications by default. For a complete list and more detailed information, see [Settings that are automatically synchronized in a UE-V deployment](uev-prepare-for-deployment.md#autosyncsettings).
|
||||
UE-V synchronizes settings for these applications by default. For a complete list and more detailed information, see [Settings that are automatically synchronized in a UE-V deployment](uev-prepare-for-deployment.md).
|
||||
|
||||
- Microsoft Office 2016, 2013, and 2010
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ Whether you want to synchronize settings for only default Windows applications o
|
||||
|
||||
[Deploy required UE-V features](uev-deploy-required-features.md)
|
||||
|
||||
- [Define a settings storage location](uev-deploy-required-features.md#ssl)
|
||||
- [Define a settings storage location](uev-deploy-required-features.md)
|
||||
|
||||
- [Enable the UE-V service](uev-deploy-required-features.md#enable-the-ue-v-service) on user computers
|
||||
|
||||
@ -33,9 +33,9 @@ If you want to use UE-V to synchronize user-defined settings for custom applicat
|
||||
|
||||
- [Install the UE-V template generator](uev-deploy-uev-for-custom-applications.md#install-the-uev-template-generator) so you can create, edit, and validate the custom settings location templates required to synchronize custom application settings
|
||||
|
||||
- [Create custom settings location templates](uev-deploy-uev-for-custom-applications.md#createcustomtemplates) with the UE-V template generator
|
||||
- [Create custom settings location templates](uev-deploy-uev-for-custom-applications.md) with the UE-V template generator
|
||||
|
||||
- [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md#deploycatalogue) to store your custom settings location templates
|
||||
- [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md) to store your custom settings location templates
|
||||
|
||||
The workflow diagram below illustrates a typical UE-V deployment and the decisions you need to be prepared to make.
|
||||
|
||||
@ -310,7 +310,7 @@ The UE-V settings storage location and settings template catalog support storing
|
||||
|
||||
In addition, because SYSVOL uses DFSR for replication, SYSVOL cannot be used for UE-V data file replication.
|
||||
|
||||
- Configure the share permissions and NTFS access control lists (ACLs) as specified in [Deploying the settings storage location for UE-V](uev-deploy-required-features.md#ssl).
|
||||
- Configure the share permissions and NTFS access control lists (ACLs) as specified in [Deploying the settings storage location for UE-V](uev-deploy-required-features.md).
|
||||
|
||||
- Use file server clustering along with the UE-V service to provide access to copies of user state data in the event of communications failures.
|
||||
|
||||
|
||||
@ -132,7 +132,7 @@ You can deploy UE-V settings location template with the following methods:
|
||||
|
||||
For more information about using UE-V and Windows PowerShell, see [Managing UE-V settings location templates using Windows PowerShell and WMI](uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md).
|
||||
|
||||
- **Registering template with Template Catalog Path**. If you use the Settings Template Catalog Path to manage templates on users’ computers, copy the Office template into the folder defined in the UE-V service. The next time the Template Auto Update (ApplySettingsCatalog.exe) scheduled task runs, the settings location template will be registered on the device. For more information, see [Deploy a settings template catalog](uev-deploy-uev-for-custom-applications.md#deployasettingstemplatecatalog).
|
||||
- **Registering template with Template Catalog Path**. If you use the Settings Template Catalog Path to manage templates on users’ computers, copy the Office template into the folder defined in the UE-V service. The next time the Template Auto Update (ApplySettingsCatalog.exe) scheduled task runs, the settings location template will be registered on the device. For more information, see [Deploy a settings template catalog](uev-deploy-uev-for-custom-applications.md).
|
||||
|
||||
- **Registering template with Configuration Manager**. If you use Configuration Manager to manage your UE-V settings storage templates, recreate the Template Baseline CAB, import it into Configuration Manager, and then deploy the baseline to user devices. For more information, see the guidance provided in the documentation for the [System Center 2012 Configuration Pack for Microsoft User Experience Virtualization 2.0](https://www.microsoft.com/en-us/download/details.aspx?id=40913).
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ UE-V monitors when an application opens by the program name and, optionally, by
|
||||
|
||||
**To implement settings synchronization for a virtualized application**
|
||||
|
||||
1. Run the UE-V template generator to collect the settings of the locally installed application whose settings you want to synchronize between computers. This process creates a settings location template. If you use a built-in template such as a Microsoft Office template, skip this step. For more information about using the UE-V template generator, see [Deploy UE-V for custom applications](uev-deploy-uev-for-custom-applications.md#createcustomtemplates).
|
||||
1. Run the UE-V template generator to collect the settings of the locally installed application whose settings you want to synchronize between computers. This process creates a settings location template. If you use a built-in template such as a Microsoft Office template, skip this step. For more information about using the UE-V template generator, see [Deploy UE-V for custom applications](uev-deploy-uev-for-custom-applications.md).
|
||||
|
||||
2. Install the App-V application package if you have not already done so.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user