Finished recreating tables in articles I have so far.

HTML will be removed after I've checked table accuracy.

windows/application-management/app-v/revision-heidi/appv-reporting.md

@@ -143,6 +143,16 @@ This example command specifies the maximum size of the data block as 10,240 MB.
 
 The following table displays the types of information you can collect by using App-V reporting.
 
+|Client information|Package information|Application usage|
+|---|---|---|
+|Host name|Package name|Start and end times|
+|App-V client version|Package version|Run status|
+|Processor architecture|Package source|Shutdown state|
+|Operating system version|Percent cached|Application name|
+|Service Pack level||Application version|
+|Operating system type||Username|
+|||Connection group|
+
 <table>
 <colgroup>
 <col width="33%" />
@@ -221,6 +231,13 @@ The **-DeleteOnSuccess** parameter indicates that if the transfer is successful,
 
 You can also use the **Send-AppVClientReport** cmdlet to manually collect data. This solution is helpful with or without an existing reporting server. The following list displays information about collecting data with or without a reporting server.
 
+|With a reporting server|Without a reporting server|
+|---|---|
+|f you have an existing App-V reporting server, create a customized scheduled task or script. Specify that the client sends the data to the specified location at the desired frequency.|If you do not have an existing App-V reporting Server, use the **–URL** parameter to send the data to a specified share. For example: ```Send-AppVClientReport –URL \\Myshare\MyData\ -DeleteOnSuccess``` <br>The previous example will send the reporting data to the ```\\MyShare\MyData\``` location indicated by the **-URL** parameter. After the data has been sent, the cache is cleared.|
+
+>[!NOTE]
+>If a location other than the Reporting Server is specified, the data is sent in **.xml** format with no additional processing.
+
 <table>
 <colgroup>
 <col width="50%" />
@@ -269,9 +286,7 @@ You should also ensure that the reporting server web service’s **Maximum Concu
 
 ## Have a suggestion for App-V?
 
-Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
-
-For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
+Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
 
 ## Related topics
 

windows/application-management/app-v/revision-heidi/appv-security-considerations.md

@@ -38,10 +38,17 @@ A best practice for user account management is to create domain global groups an
 >[!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.
 
-### <a href="" id="-------------app-v-5-1-server-security"></a> App-V server security
+### 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.
 
+|Group name|Details|Important notes|
+|---|---|
+|App-V Management Admin group|Used to manage the App-V management server. This group is created during the App-V Management Server installation.|The management console can't create a new group after installation is complete.|
+|Database read/write for Management Service account|Provides read/write access to the management database. This account should be created during App-V management database installation.||
+|App-V Management Service install admin account|Provides public access to schema-version table in management database. This account should be created during App-V management database installation.|This is only required if the management database is being installed separately from the service.|
+|App-V Reporting Service install admin account|Public access to schema-version table in reporting database. This account should be created during the App-V reporting database installation.|This is only required if reporting database is being installed separately from the service.|
+
 <table>
 <colgroup>
 <col width="50%" />

windows/application-management/app-v/revision-heidi/appv-supported-configurations.md

@@ -51,6 +51,13 @@ You can install the App-V Management server on a server running Windows Server 2
 
 The following table lists the SQL Server versions that the App-V Management database installation supports.
 
+|SQL Server version|Service pack|System architecture|
+|---|---|---|
+|Microsoft SQL Server 2014||32-bit or 64-bit|
+|Microsoft SQL Server 2012|SP2|32-bit or 64-bit|
+|Microsoft SQL Server 2008 R2|SP3|32-bit or 64-bit|
+
+
 <table>
 <colgroup>
 <col width="33%" />
@@ -115,6 +122,12 @@ App-V adds no additional requirements beyond those of Windows Server.
 
 The following table lists the SQL Server versions that are supported for the App-V Reporting database installation.
 
+|SQL Server version|Service pack|System architecture|
+|---|---|---|
+|Microsoft SQL Server 2014||32-bit or 64-bit|
+|Microsoft SQL Server 2012|SP2|32-bit or 64-bit|
+|Microsoft SQL Server 2008 R2|SP3|32-bit or 64-bit|
+
 <table>
 <colgroup>
 <col width="33%" />
@@ -157,6 +170,16 @@ Similarly, the App-V Remote Desktop Services (RDS) client is included with Windo
 
 The following table lists the operating systems that the App-V Sequencer installation supports.
 
+|Operating system|Service pack|System architecture|
+|---|---|---|
+|Microsoft Windows Server 2012 R2||64-bit|
+|Microsoft Windows Server 2012||64-bit|
+|Microsoft Windows Server 2008 R2|SP1|64-bit|
+|Microsoft Windows 10||32-bit and 64-bit|
+|Microsoft Windows 8.1||32-bit and 64-bit|
+|Microsoft Windows 8||32-bit and 64-bit|
+|Microsoft Windows 7|SP1|32-bit and 64-bit|
+
 <table>
 <colgroup>
 <col width="33%" />