So there is no question of warranty since the upgrade can take place anytime after warranty ends also. Now Dell itself may take this as 'tampering with original factory installed OS'.. OS upgrade is a big issue. So can we expect Dell to consider solving this by offering a legit link vide email for specific Service Tag and Express Sevice Code whereby there is authentication as well as solution?
Request Dell to reply. Browse Community. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Last reply by VerbalRender Unsolved.
All forum topics Previous Topic Next Topic. Replies 2. NemesisDB 7 Gold. No promises, but the compatibility website seems to think that 1. If you are already performing a Windows deployment to Surface devices in your organization, it is quick and easy to add the installation files for each protocol to your deployment share and configure automatic installation during deployment. You can even configure a task sequence that updates previously deployed Surface devices to provide support for these protocols using the same process.
Download and extract the installation files for each protocol to separate folders in an easily accessible location. Although in some simple deployment scenarios it might be sufficient to have technicians select each package at the time of deployment, it is not recommended. This practice introduces the possibility that a technician could attempt to apply these packages to computers other than Surface devices, or that a Surface device could be deployed without EAP support due to human error.
To hide these applications from the Install Applications page, select the Hide this application in the Deployment Wizard checkbox in the properties of each application. After the applications are hidden, they will not be displayed as optional applications during deployment. To deploy them in your Surface deployment task sequence, they must be explicitly defined for installation through a separate step in the task sequence. This is typically found between the pre-application and post-application Windows Update steps.
Use the Add button to create a new Install Application step from the General category. Select Install a single application in the step Properties tab.
Simply import each MSI file as an application from the Software Library and configure a deployment to your Surface device collection. For more information on how to deploy applications with Configuration Manager, see Create and deploy an application with Configuration Manager.
0コメント