Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - whiggs

Pages: [1]
Whenever I try to build my Win10 PESE media, I always get the following error when the build process reaches the powershell component script:
Cannot create file "%BaseDir%\Target\Win10PESE\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Computer Management\desktop.ini". Access is denied: [IniWrite,#2\desktop.ini,#3,#4,#5]
I have run the application with administrator rights, so I know that permissions is not the issue.  Rather, I believe it is, due to the prompts that I receive when I delete the contents from the hard drive, that the path that the application is trying to write the file to exceeds the 260 character Path limit that is a limitation of windows.  My question is how do I get around this in order to make the build succeed?  The folder which contains the application is already in the root of one of my slave drives and the folder name is 2 characters.  Please advise.

Win10PE SE HomePage / Getwaiktools plugin question
« on: May 03, 2017, 08:40:54 AM »
Hello the Oven community.  I had a question in regards to the GetWaiktools script which downloads the necessary deployment tools which are normally included in the adk installation for use in the building and configuring of Windows 10 PESE.  More specifically, as you may or may not know, microsoft has released a new version of the Windows 10 adk for each new major update of windows 10 that has been released, including new versions of the tools included within.  So my question is how does the script know which version of the ADK tools to download and use when the script is run.  Does it scan the source media and use that to download the right version?  Does it not check at all and download only a specific version that is specifically specified in the script?  If the answer to this question is the latter of the two scenarios, then it would probably be a good idea to update the script so that it downloads the version of the ADK tools that match the version of Windows 10 that is being used as the source.  But this is a question to which I would like to get an answer to.  Thanks in advance.

Win10PE SE HomePage / Quick question.
« on: February 11, 2017, 01:14:19 AM »
Hello "theOven" Community.
So I have been using WinPESE for about 3 years now, and love what the tool can do.  Absolutely spectacular tool guys.  I haven't had any issues with the product (well, none that weren't answered by reading the forums anyway), but I did have one question about the tool in general.  Is there a way to replace the standard Windows Recovery environment with a Wim created with WinpeSE.  I have tried doing something like this during an os deployment, but instead of using WinRE, I try to use a wim created with WINPESE and activate it with Reagentc tool, but I get error "not a valid Winre image" or something around those lines.  The closest that I have gotten to my goal is to extract the contents of a WinpeSE iso to a bootable partition and edit boot menu to include that partition when booting.  So while I have kind of sort of gotten it to work, I would like to do it, for lack of a better phrase, "the right way."

ok.  so I wrote an autoit script order to automate the steps in deploying windows to client devices: 1) first the user was prompted to enter the computer name into an input box which the script would then use to edit the portion of the unattend.xml file used in step 3 relating to computer name, 2) the script would then format the C: drive of the client device to prepare it for the operating system installation, and 3) using WinNTsetup's command line arguments, automatically configure and begin installation of the operating system to the device.  Only 1 of the three steps outlined above did not complete successfully no matter what I tried, and believe it or not, it the one that would appear to be the most simple: formatting the C drive.  I believe the problem most stems either from the fact that the "windows" folder containing the system32 files is mapped to the X: drive, and not C:, or it may be due to the fact that for the line of script in question (Code is:    RunWait ( @Comspec & " /c X:\windows\system32\format C: /FS:NTFS /q /x /v:Windows /y" )uses the Comspec macro, but regardless, even calling the function with its full path did not work, so I was forced to improvise and creat a batch script which then called a modified version of the above script (which just had part 1), then would perform format and launch installation.  It would be great if this could be fixed, as autoit is one of favorite scripting languages. 

Win10PE SE HomePage / windows setup tool
« on: May 08, 2016, 11:56:57 AM »
So I had a question concerning the winNTsetup3 tool that is found in "system tools" > "Windows setup" in the start menu.  When you select "setup" and the "ready?" screen pops up to confirm the all aspects of the install, my question is regarding the "Run after" input.  Say I want to include a script that is run after the setup is complete.  I know that it is included in the OEM folder, but where does the tool look for the OEM folder?  Does it generate it itself, do I have to create it and if so where should I store it for the tool to use it?  Just some general instructions on how to use that aspect of the tool would be very appreciated.

Win10PE SE HomePage / Running MDT task sequence in Win10PESE
« on: May 04, 2016, 03:28:06 AM »
Hey all.  So I have a strange issue that I hope you might be able to help.  I used Microsoft deployment toolkit update 2 to create an offline media which would deploy and configure a Windows 10 operating system.  I would, if possible, like to actually run the task sequence from within win10pese, so that the users can go off and do other things while they wait.  And, to my surprise, when I launched "LiteTouch.vbs", the script which starts the task sequence for the deployment, it actually seemed to be working, up until the part where the operating system was supposed to install.  Just before the os install, a screen popped up asking for credentials to a network share, which shouldn't occur when using offline (as in not using a pxe server) media to deploy the operating system.  Then when the task sequence gets to the part where for installing the os, it automatically fails with unknown error.  I looked at the drives in "my computer" after one such failure, and it seems that the script which formats and partitions the drives for os deployment is not working correctly, producing some weird results.  Can anyone else offer a comment on how to resolve this?

Pages: [1]
Powered by EzPortal