startmenu layout MDT

Question

I am using MDT 2004 version and deploying Windows 10 Enterprise computers through WDS on Windows server 2022.

After configuring the custom start and taskbar layout I get the following error:

Not sure why this error occurs, because it worked before just fine.

Answer 1

Hi,

Thank you for posting in Microsoft Q&A forum.

How about changing the -layoutpath like below?

Import-startlayout -layoutpath "%scriproot%\mes_scriptes\custommenu.xml" -Mountpath $env:SystemDrive

Refer to: How to Deploy Custom Start Menu with MDT

Note: This is non-Microsoft link, just for your reference.

Thanks for your time. Have a nice day!

Best regards,

Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hello,

Thank you for your question and for reaching out with your question today.

The error "Import startlayout cannot find file" typically occurs when the custom start and taskbar layout file specified in your deployment cannot be found by the system during the deployment process. There are a few common reasons why this error might occur, and I'll outline some troubleshooting steps to help you resolve the issue:

1. Check File Path: Double-check the file path you have specified for the custom start and taskbar layout file in your MDT deployment task sequence. Ensure that the file exists in the specified location and that the path is correct.
2. File Access Permissions: Verify that the deployment process has the necessary permissions to access the custom start and taskbar layout file. If the file is located on a network share, ensure that the deployment account has appropriate read access to the share and the file.
3. UNC vs. Local Path: Depending on how you are referencing the custom layout file, ensure that you are using either a UNC path (\server\share\customlayout.xml) or a local path (C:\customlayout.xml) consistently throughout your deployment settings.
4. Network Connectivity: Check the network connectivity between the deployment server and the location where the custom layout file is stored. Ensure that there are no network issues or firewall rules that might be blocking access to the file.
5. Drive Mapping: If you are using a network share for the custom layout file, consider using a fully qualified UNC path (\server\share\customlayout.xml) rather than relying on mapped network drives, as mapped drives might not be available during the deployment process.
6. Deployment Share Update: If you have made changes to the custom layout file or its location, remember to update your MDT deployment share to ensure the latest files are available during the deployment.
7. Syntax and XML Validation: Review the custom layout file itself for any syntax errors or XML validation issues that might be causing the problem.
8. Test with Local File: As a troubleshooting step, try copying the custom layout file directly to the local system drive (e.g., C:\customlayout.xml) and update your task sequence to reference the local path. This will help determine if the issue is related to the file location or something else in the deployment process.
9. Log Files: Review the MDT deployment log files (e.g., BDD.log) for any additional error messages or clues about why the file cannot be found.

By going through these troubleshooting steps, you should be able to identify the cause of the "Import startlayout cannot find file" error and resolve the issue in your MDT deployment. As always, make sure to back up your deployment configuration and test any changes in a lab environment before applying them to production deployments.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.