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

Merge pull request #4421 from nschonni/fix--MD038/no-space-in-code

Browse Source 
fix: MD038/no-space-in-code
This commit is contained in:
Daniel Simpson 2019-07-17 17:24:56 -07:00 committed by GitHub
commit b9e417fb0c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
22 changed files with 229 additions and 213 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
mdop/appv-v5/how-to-install-the-publishing-server-on-a-remote-computer.md
View File

@ -51,21 +51,16 @@ Use the following procedure to install the publishing server on a separate compu
9. To verify if the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: <strong>http://publishingserver:pubport</strong>. If the server is running correctly information similar to the following will be displayed:
`<Publishing Protocol="1.0">`
` <Packages>`
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
` </Packages>`
` <NoGroup>`
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
` </NoGroup>`
`</Publishing>`
```xml
<Publishing Protocol="1.0">
<Packages>
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
</Packages>
<NoGroup>
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
</NoGroup>
</Publishing>
```
**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).

25
mdop/appv-v5/how-to-install-the-publishing-server-on-a-remote-computer51.md
View File

@ -51,21 +51,16 @@ Use the following procedure to install the publishing server on a separate compu
9. To verify if the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: <strong>http://publishingserver:pubport</strong>. If the server is running correctly information similar to the following will be displayed:
`<Publishing Protocol="1.0">`
` <Packages>`
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
` </Packages>`
` <NoGroup>`
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
` </NoGroup>`
`</Publishing>`
```xml
<Publishing Protocol="1.0">
<Packages>
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
</Packages>
<NoGroup>
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
</NoGroup>
</Publishing>
```
**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).

130
mdop/mbam-v1/how-to-move-mbam-10-features-to-another-computer.md
View File

@ -88,49 +88,55 @@ You can use the following procedure to move the MBAM Recovery and Hardware Datab
Modify the MBAM Recovery and Hardware Database to use the full recovery mode.
`USE master;`
```sql
USE master;
`GO`
GO
`ALTER DATABASE "MBAM Recovery and Hardware"`
ALTER DATABASE "MBAM Recovery and Hardware"
` SET RECOVERY FULL;`
SET RECOVERY FULL;
`GO`
GO
```
Create MBAM Recovery and Hardware Database Data and MBAM Recovery logical backup devices.
`USE master`
```sql
USE master
`GO`
GO
`EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',`
EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',
`'Z:\MBAM Recovery and Hardware Database Data.bak';`
'Z:\MBAM Recovery and Hardware Database Data.bak';
`GO`
GO
```
Back up the full MBAM Recovery and Hardware database.
`BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];`
```sql
BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];
`GO`
GO
`BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]`
BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]
`TO FILE = 'Z:\SQLServerInstanceCertificateFile'`
TO FILE = 'Z:\SQLServerInstanceCertificateFile'
`WITH PRIVATE KEY`
WITH PRIVATE KEY
`(`
(
` FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
` ENCRYPTION BY PASSWORD = '$PASSWORD$'`
ENCRYPTION BY PASSWORD = '$PASSWORD$'
`);`
);
`GO`
GO
```
**Note**
Replace the values from the preceding example with those that match your environment:
@ -181,43 +187,51 @@ You can use the following procedure to move the MBAM Recovery and Hardware Datab
4. To automate this procedure, create a SQL file (.sql) that contains the following SQL script:
`-- Restore MBAM Recovery and Hardware Database. `
```sql
-- Restore MBAM Recovery and Hardware Database.
`USE master`
USE master
`GO`
GO
```
Drop the certificate created by MBAM Setup.
`DROP CERTIFICATE [MBAM Recovery Encryption Certificate]`
```sql
DROP CERTIFICATE [MBAM Recovery Encryption Certificate]
`GO`
GO
```
Add certificate
`CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]`
```sql
CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]
`FROM FILE = 'Z: \SQLServerInstanceCertificateFile'`
FROM FILE = 'Z: \SQLServerInstanceCertificateFile'
`WITH PRIVATE KEY`
WITH PRIVATE KEY
`(`
(
` FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
` DECRYPTION BY PASSWORD = '$PASSWORD$'`
DECRYPTION BY PASSWORD = '$PASSWORD$'
`);`
);
`GO`
GO
```
Restore the MBAM Recovery and Hardware database data and the log files.
`RESTORE DATABASE [MBAM Recovery and Hardware]`
```sql
RESTORE DATABASE [MBAM Recovery and Hardware]
` FROM DISK = 'Z:\MBAM Recovery and Hardware Database Data.bak'`
FROM DISK = 'Z:\MBAM Recovery and Hardware Database Data.bak'
` WITH REPLACE`
WITH REPLACE
```
**Note**
Replace the values from the preceding example with those that match your environment:
@ -354,35 +368,37 @@ If you choose to move the MBAM Compliance Status Database feature from one compu
2. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
`-- Modify the MBAM Compliance Status Database to use the full recovery model.`
```sql
-- Modify the MBAM Compliance Status Database to use the full recovery model.
`USE master;`
USE master;
`GO`
GO
`ALTER DATABASE "MBAM Compliance Status"`
ALTER DATABASE "MBAM Compliance Status"
` SET RECOVERY FULL;`
SET RECOVERY FULL;
`GO`
GO
`-- Create MBAM Compliance Status Data logical backup devices.`
-- Create MBAM Compliance Status Data logical backup devices.
`USE master`
USE master
`GO`
GO
`EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',`
EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',
`'Z: \MBAM Compliance Status Database Data.bak';`
'Z: \MBAM Compliance Status Database Data.bak';
`GO`
GO
-- Back up the full MBAM Recovery and Hardware database.
`BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];`
BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];
`GO`
GO
```
3. Run the SQL file with a command that is similar to the following one, by using the SQL Server PowerShell:
@ -422,19 +438,21 @@ If you choose to move the MBAM Compliance Status Database feature from one compu
3. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
`-- Create MBAM Compliance Status Database Data logical backup devices. `
```sql
-- Create MBAM Compliance Status Database Data logical backup devices.
`Use master`
Use master
`GO`
GO
-- Restore the MBAM Compliance Status database data files.
`RESTORE DATABASE [MBAM Compliance Status Database]`
RESTORE DATABASE [MBAM Compliance Status Database]
` FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'`
FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'
` WITH REPLACE`
WITH REPLACE
```
4. Run the SQL File with a command that is similar to the following one, by using the SQL Server PowerShell:

120
mdop/mbam-v2/how-to-move-mbam-20-features-to-another-computer-mbam-2.md
View File

@ -88,49 +88,51 @@ To move the Recovery Database from one computer to another (for example, from Se
Modify the MBAM Recovery Database to use the full recovery mode.
`USE master;`
```sql
USE master;
`GO`
GO
`ALTER DATABASE "MBAM Recovery and Hardware"`
ALTER DATABASE "MBAM Recovery and Hardware"
` SET RECOVERY FULL;`
SET RECOVERY FULL;
`GO`
GO
-- Create MBAM Recovery Database Data and MBAM Recovery logical backup devices.
`USE master`
USE master
`GO`
GO
`EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',`
EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',
`'Z:\MBAM Recovery Database Data.bak';`
'Z:\MBAM Recovery Database Data.bak';
`GO`
GO
-- Back up the full MBAM Recovery Database.
`BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];`
BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];
`GO`
GO
`BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]`
BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]
`TO FILE = 'Z:\SQLServerInstanceCertificateFile'`
TO FILE = 'Z:\SQLServerInstanceCertificateFile'
`WITH PRIVATE KEY`
WITH PRIVATE KEY
`(`
(
` FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
` ENCRYPTION BY PASSWORD = '$PASSWORD$'`
ENCRYPTION BY PASSWORD = '$PASSWORD$'
`);`
);
`GO`
GO
```
**Note**
Replace the following values in the example above with those that match your environment:
@ -183,43 +185,45 @@ To move the Recovery Database from one computer to another (for example, from Se
4. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
`-- Restore MBAM Recovery Database. `
```sql
-- Restore MBAM Recovery Database.
`USE master`
USE master
`GO`
GO
-- Drop certificate created by MBAM Setup.
`DROP CERTIFICATE [MBAM Recovery Encryption Certificate]`
DROP CERTIFICATE [MBAM Recovery Encryption Certificate]
`GO`
GO
--Add certificate
`CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]`
CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]
`FROM FILE = 'Z: \SQLServerInstanceCertificateFile'`
FROM FILE = 'Z: \SQLServerInstanceCertificateFile'
`WITH PRIVATE KEY`
WITH PRIVATE KEY
`(`
(
` FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
` DECRYPTION BY PASSWORD = '$PASSWORD$'`
DECRYPTION BY PASSWORD = '$PASSWORD$'
`);`
);
`GO`
GO
-- Restore the MBAM Recovery Database data and log files.
`RESTORE DATABASE [MBAM Recovery and Hardware]`
RESTORE DATABASE [MBAM Recovery and Hardware]
` FROM DISK = 'Z:\MBAM Recovery Database Data.bak'`
FROM DISK = 'Z:\MBAM Recovery Database Data.bak'
` WITH REPLACE`
WITH REPLACE
```
**Note**
Replace the following values in the example above with those that match your environment:
@ -362,35 +366,37 @@ If you want to move the MBAM Compliance and Audit Database from one computer to
2. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
`-- Modify the MBAM Compliance Status Database to use the full recovery model.`
```sql
-- Modify the MBAM Compliance Status Database to use the full recovery model.
`USE master;`
USE master;
`GO`
GO
`ALTER DATABASE "MBAM Compliance Status"`
ALTER DATABASE "MBAM Compliance Status"
` SET RECOVERY FULL;`
SET RECOVERY FULL;
`GO`
GO
`-- Create MBAM Compliance Status Data logical backup devices.`
-- Create MBAM Compliance Status Data logical backup devices.
`USE master`
USE master
`GO`
GO
`EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',`
EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',
`'Z: \MBAM Compliance Status Database Data.bak';`
'Z: \MBAM Compliance Status Database Data.bak';
`GO`
GO
-- Back up the full MBAM Recovery database.
`BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];`
BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];
`GO`
GO
```
3. Run the SQL file by using a Windows PowerShell command line that is similar to the following:
@ -430,19 +436,21 @@ If you want to move the MBAM Compliance and Audit Database from one computer to
3. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
`-- Create MBAM Compliance Status Database Data logical backup devices. `
```sql
-- Create MBAM Compliance Status Database Data logical backup devices.
`Use master`
Use master
`GO`
GO
-- Restore the MBAM Compliance Status database data files.
`RESTORE DATABASE [MBAM Compliance Status]`
RESTORE DATABASE [MBAM Compliance Status]
` FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'`
FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'
` WITH REPLACE`
WITH REPLACE
```
4. Run the SQL File by using a Windows PowerShell command line that is similar to the following:

2
windows/client-management/troubleshoot-windows-freeze.md
View File

@ -204,7 +204,7 @@ If the physical computer is still running in a frozen state, follow these steps
2. From a remote computer that is preferably in the same network and subnet, go to **Registry Editor** \> **Connect Network Registry**. Then, connect to the concerned computer, and verify the following settings:
* ` `*HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\CrashDumpEnabled`
* `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\CrashDumpEnabled`
Make sure that the [CrashDumpEnabled](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-2000-server/cc976050(v=technet.10)) registry entry is `1`.