From bdf64935ff36fb33a9675127dab272a2ff69e2c5 Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Tue, 9 Aug 2016 14:50:54 -0700 Subject: [PATCH 1/3] Fixed server version strings --- windows/manage/appv-security-considerations.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/manage/appv-security-considerations.md b/windows/manage/appv-security-considerations.md index 79d71d971a..0a114d5036 100644 --- a/windows/manage/appv-security-considerations.md +++ b/windows/manage/appv-security-considerations.md @@ -29,7 +29,7 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa **Understand the security risks.** The most serious risk to App-V is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V clients. The loss of App-V functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact. -**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver. +**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V 5.1 server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V 5.1 servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver. **Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, subscribe to the Security Notification service (). @@ -38,7 +38,7 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa ## Accounts and groups in App-V -A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V local groups on the App-V servers. +A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V local groups on the App-V 5.1 servers. **Note**   App-V client computer accounts that need to connect to the publishing server must be part of the publishing server’s **Users** local group. By default, all computers in the domain are part of the **Authorized Users** group, which is part of the **Users** local group. @@ -47,7 +47,7 @@ App-V client computer accounts that need to connect to the publishing server mus ### App-V server security -No groups are created automatically during App-V Setup. You should create the following Active Directory Domain Services global groups to manage App-V server operations. +No groups are created automatically during App-V Setup. You should create the following Active Directory Domain Services global groups to manage App-V 5.1 server operations. From a09d5a04a249229d00b48ec6dfa609e8d5e1a81f Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Tue, 9 Aug 2016 15:02:40 -0700 Subject: [PATCH 2/3] Updated four topic titles --- windows/manage/TOC.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index b46f78d870..a976bf9afc 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -52,7 +52,7 @@ ##### [App-V Capacity Planning](appv-capacity-planning.md) ##### [Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md) ##### [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md) -##### [Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md) +##### [Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md) ##### [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md) ##### [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md) ##### [Planning for Using App-V with Office](appv-planning-for-using-appv-with-office.md) @@ -65,9 +65,9 @@ ##### [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md) ##### [How to Install the Sequencer](appv-install-the-sequencer.md) ##### [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md) -#### [Deploying the App-V Server](appv-deploying-the-appv-server.md) -##### [How to Deploy the App-V Server](appv-deploy-the-appv-server.md) -##### [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md) +#### [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md) +##### [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md) +##### [How to Deploy the App-V 5.1 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md) ##### [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md) ##### [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md) ##### [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md) From 11c8f5863c6979cbb64cdb324351ae3a59b46566 Mon Sep 17 00:00:00 2001 From: Justinha Date: Tue, 9 Aug 2016 16:03:59 -0700 Subject: [PATCH 3/3] added ProviderType to inf file --- windows/keep-secure/bitlocker-how-to-enable-network-unlock.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/keep-secure/bitlocker-how-to-enable-network-unlock.md b/windows/keep-secure/bitlocker-how-to-enable-network-unlock.md index 16e0aa12b2..1884657372 100644 --- a/windows/keep-secure/bitlocker-how-to-enable-network-unlock.md +++ b/windows/keep-secure/bitlocker-how-to-enable-network-unlock.md @@ -149,6 +149,7 @@ To create a self-signed certificate, do the following: ``` syntax [NewRequest] Subject="CN=BitLocker Network Unlock certificate" + ProviderType=0 Exportable=true RequestType=Cert KeyUsage="CERT_KEY_ENCIPHERMENT_KEY_USAGE"