mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-27 00:03:45 +00:00
Adding content
This commit is contained in:
LizRoss
@ -43,7 +43,7 @@
|
||||
###[Use the Enterprise Mode Site List Portal](ie11-deploy-guide/use-the-enterprise-mode-portal.md)
|
||||
####[Set up the Enterprise Mode Site List Portal](ie11-deploy-guide/set-up-enterprise-mode-portal.md)
|
||||
#####[Create a change request using the Enterprise Mode Site List Portal](ie11-deploy-guide/create-change-request-enterprise-mode-portal.md)
|
||||
#####[Rollback changes in the pre-production environment using the Enterprise Mode Site List Portal](ie11-deploy-guide/rollback-changes-pre-production-environment-enterprise-mode-portal.md)
|
||||
#####[Verify your changes using the Enterprise Mode Site List Portal](ie11-deploy-guide/verify-changes-enterprise-mode-portal.md)
|
||||
#####[Approve a change request using the Enterprise Mode Site List Portal](ie11-deploy-guide/approve-change-request-enterprise-mode-portal.md)
|
||||
#####[Schedule a production environment change using the Enterprise Mode Site List Portal](ie11-deploy-guide/schedule-production-change-enterprise-mode-portal.md)
|
||||
#####[Rollback changes in the production environment using the Enterprise Mode Site List Portal](ie11-deploy-guide/rollback-changes-production-environment-enterprise-mode-portal.md)
|
||||
|
||||
@ -22,14 +22,14 @@ ms.sitesec: library
|
||||
Employees assigned to the Requester role all have the ability to create a change request. A change request is used to tell the Approvers and the Administrator that a website needs to be added or removed from the Enterprise Mode Site List. The employee can navigate to each stage of the process by using the workflow links provided at the top of each page of the portal.
|
||||
|
||||
>[!Important]
|
||||
>Each requester must have a test machine that lets them use the pre-production environment to ensure that the requested change is correct.
|
||||
>Each Requester must have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
|
||||
**To create a new change request**
|
||||
1. The Requester (an employee that has been assigned the Requester role) signs into the Enterprise Mode Site List Portal, and clicks **Create new request**.
|
||||
|
||||
The **Create new request** screen appears.
|
||||
|
||||
2. Fill out all of the required fields, based on your group and the app, including:
|
||||
2. Fill out all of the required fields, based on the group and the app, including:
|
||||
|
||||
- **Group name.** Select the name of your group from the dropdown box.
|
||||
|
||||
@ -55,7 +55,7 @@ Employees assigned to the Requester role all have the ability to create a change
|
||||
|
||||
- **Is an x-ua tag used?** Select **Yes** or **No** whether an x-ua-compatible tag is used by the app. For more info about x-ua-compatible tags, see the topcis in [Defining document compatibility](https://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx).
|
||||
|
||||
4. Click **Save and continue** to save your request and get the app info sent to the pre-production environment site list for testing.
|
||||
4. Click **Save and continue** to save the request and get the app info sent to the pre-production environment site list for testing.
|
||||
|
||||
A message appears that the request was successful, including a **Request ID** number, saying that the change is being made to the pre-production environment site list.
|
||||
|
||||
@ -65,38 +65,5 @@ Employees assigned to the Requester role all have the ability to create a change
|
||||
|
||||
- **If the change is incorrect.** The Requester can rollback the change in pre-production or ask for help from the Administrator.
|
||||
|
||||
|
||||
**To edit an existing change request**
|
||||
1. The Requester (an employee that has been assigned the Requester role) signs into the Enterprise Mode Site List Portal, and clicks the **Request ID** for their active request.
|
||||
|
||||
2. Update any of the info, and then click **Save and continue**.
|
||||
|
||||
A message appears that the request was successful, including a **Request ID** number, and saying that the change is being made to the pre-production environment site list.
|
||||
|
||||
3. The requester gets an email that includes:
|
||||
|
||||
- A batch script, that when run, configures the test machine for the pre-production environment.
|
||||
|
||||
- The necessary steps to make sure that the changed info is correct.
|
||||
|
||||
- **If the change is correct.** The Requester asks the approvers to approve the change request by selecting **Successful** and clicking **Send for approval**.
|
||||
|
||||
- **If the change is incorrect.** The Requester can rollback the change in pre-production or ask for help from the Administrator.
|
||||
|
||||
|
||||
**To delete an unapproved or no longer relevant change request**
|
||||
1. The Requester (an employee that has been assigned the Requester role) signs into the Enterprise Mode Site List Portal, and clicks **Create new request**.
|
||||
|
||||
2. Update any of the request fields, and then click **Save and continue**.
|
||||
|
||||
A message appears that the update was successful, including a **Request ID** number, and saying that the change is being made to the pre-production environment site list.
|
||||
|
||||
3. The requester gets an email that includes:
|
||||
|
||||
- A batch script, that when run, configures the test machine for the pre-production environment.
|
||||
|
||||
- The necessary steps to make sure that the changed info is correct.
|
||||
|
||||
- **If the change is correct.** The Requester asks the approvers to approve the change request by selecting **Successful** and clicking **Send for approval**.
|
||||
|
||||
- **If the change is incorrect.** The Requester can rollback the change in pre-production or ask for help from the Administrator.
|
||||
## Next steps
|
||||
After the change request is created, the Requester must make sure the suggested changes work in the pre-production environment. For these steps, see the [Verify your changes using the Enterprise Mode Site List Portal](verify-changes-enterprise-mode-portal.md) topic.
|
||||
@ -0,0 +1,53 @@
|
||||
---
|
||||
localizationpriority: low
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: appcompat
|
||||
description: Details about how to make sure your change request info is accurate within the pre-production environment of the Enterprise Mode Site List Portal.
|
||||
author: eross-msft
|
||||
ms.prod: ie11
|
||||
title: Verify your changes using the Enterprise Mode Site List Portal (Internet Explorer 11 for IT Pros)
|
||||
ms.sitesec: library
|
||||
---
|
||||
|
||||
# Verify your changes using the Enterprise Mode Site List Portal
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2008 R2 with Service Pack 1 (SP1)
|
||||
|
||||
>[!Important]
|
||||
>This step requires that each Requester have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
|
||||
|
||||
After the Requester successfully submits a change request to the Enterprise Mode Site List Portal, he or she gets an email, including:
|
||||
|
||||
- **EMIE_RegKey**. A batch file that when run, sets the registry key to point to the local pre-production Enterprise Mode Site List.
|
||||
|
||||
- **Test steps**. The suggested steps about how to test the change request details to make sure they're accurate in the pre-production environment.
|
||||
|
||||
- **EMIE_Reset**. A batch file that when run, reverts the changes made to the pre-production registry.
|
||||
|
||||
## Certify your results in the pre-production environment
|
||||
After the Requester tests the changes, he or she must go back into the Enterprise Mode Site List Portal, **Pre-production verification** screen to certify whether the testing was successful.
|
||||
|
||||
**To certify changes and send to approvers**
|
||||
1. On the **Pre-production verification** screen, the Requester clicks **Successful** and optionally includes any attachments (only .jpeg, .png, .jpg and .txt files are allowed) to support the change request and testing results.
|
||||
|
||||
2. The Requester reviews the pre-defined approvers, and then clicks **Send for approval**.
|
||||
|
||||
**To rollback your pre-production changes**
|
||||
1. On the **Pre-production verification** screen, the Requester clicks **Failed** and optionally includes any attachments (only .jpeg, .png, .jpg and .txt files are allowed) to support the change request and testing results.
|
||||
|
||||
2. Add a description about the issue into the **Issue description** box, and then click **Send failure details**.
|
||||
|
||||
The change request and issue info are sent to the Administrators.
|
||||
|
||||
3. The Requester clicks **Roll back** to roll back the changes in the pre-production environment.
|
||||
|
||||
After the Requester rolls back the changes, he or she can update the requst and re-submit the ticket.
|
||||
|
||||
## Next steps
|
||||
If the change request is certified as successful, the Requester must next send it to the Approvers for approval. For the Approver-related steps, see the [Approve a change request using the Enterprise Mode Site List Portal](approve-change-request-enterprise-mode-portal.md) topic.
|
||||
Reference in New Issue
Block a user