Deilson Oliveira

I created an offline media of the Windows 20H2, where I have two Windows version options, I'll call version A and version B Version A: is a standard task sequence, which disables the bitlocker, partitions the disk, installs install.wim, installs the configuration manager, restarts, then adds 3 programs, which are: 7Zip, Adobe and Notepad++, and finishes Version B: identical to version A, but without 7zip. The most bizarre thing is that in version B, everything works without a problem. But in version A, at the end of the Task Sequence (NOTE: I use TSBackground, but that's not the problem, otherwise it would affect both versions) the success screen appears, and I click the Finish button, and then I go to a screen blue (not the BSOD) saying: "Sign-in process initialization failure, Interactive logon process initialization has failed. Please consult the event log for more details." How is this possible if the difference between them is just 7zip? This screen does not corrupt the system, it only appears once, restarts, and I can log in again without any problems, and 7Zip is still there without any problem, and consulting the smsts.log, 7Zip is terminated with Exit Code 0. This error does not interfere with nothing, but it bothers me a lot, even more that I will distribute this system to more than 2,000 machines, everyone will have doubts about this screen, and this is not pleasant to leave showing. I googled it, but it seems that it happens when it really corrupts the system, in my case it doesn't, it shows up once, but I wanted to understand why the hell it shows up because of a 7Zip (already tested it with msi version, exe, old version, version new, and etc and with no result, I tried to put another program in place, like CCleaner for example and it causes the same result) I created an offline media, where I have two Windows version options, I'll call version A and version B Version A: is a standard task sequence, which disables the bitlocker, partitions the disk, installs install.wim, installs the configuration manager, restarts, then adds 3 programs, which are: 7Zip, Adobe and Notepad++, and finishes Version B: identical to version A, but without 7zip. The most bizarre thing is that in version B, everything works without a problem. But in version A, at the end of the Task Sequence (NOTE: I use TSBackground, but that's not the problem, otherwise it would affect both versions) the success screen appears, and I click the Finish button, and then I go to a screen blue (not the BSOD) saying: "Sign-in process initialization failure, Interactive logon process initialization has failed. Please consult the event log for more details." How is this possible if the difference between them is just 7zip? This screen does not corrupt the system, it only appears once, restarts, and I can log in again without any problems, and 7Zip is still there without any problem, and consulting the smsts.log, 7Zip is terminated with Exit Code 0. This error does not interfere with nothing, but it bothers me a lot, even more that I will distribute this system to more than 2,000 machines, everyone will have doubts about this screen, and this is not pleasant to leave showing. I googled it, but it seems that it happens when it really corrupts the system, in my case it doesn't, it shows up once, but I wanted to understand why the hell it shows up because of a 7Zip (already tested it with msi version, exe, old version, version new, and etc and with no result, I tried to put another program in place, like CCleaner for example and it causes the same result) (Note, the 2004 version I've never seen this happen and it's the same Task Sequence, I just changed install.wim to the new 20H2 version)

In the company I work for, there are situations where internet access is very bad, so we deploy the image using offline media (putting the USB on the computer and installing the image from there). And there are also regions where it is difficult for us to hire temporary analysts to make some demands.So I thought of an alternative to prevent our analysts who are on the users' end from always deploying when the computer has startup problems.I was wondering if it could work like this:1- The installation is performed normally, but in the part of creating the partitions, if you create a partition with a predefined size like 10GB for example or use the size of "install.wim" as size reference, and that this partition was hidden for that the end user does not see its existence. After that the Task Sequence continues normally performing the install.wim installation, applying customizations, installing programs and running scripts and so on.2- At the end of the Task Sequence, a clone of the partition where install.wim was installed (C:\ normally) was performed to this hidden partition, creating a backup.wim for example, and here is the part where I don't know what to think , the idea I had is to create a custom boot.wim where it would be possible to clean the C:\ partition (which would be having problems in the future) and extract this backup.wim to the C:\ disk (Similar to Dell Assist Image) and point in the BCD file so there is a second boot menu that would be this custom boot.wim. What I don't know is how this boot.wim would be built, it would only be customized with .bat batch files, or a SCCM boot.wim that loads 5 task sequence only, where 1 would erase C:\ 2 partitions - Recreate the partitions again, 3 extract the backup.wim there. 4- Configure the BCD but without removing the second menu which would be the recovery boot.wim, and 5- restart the computer and work normally.I know it's extremely complex, but I need to think outside the box to save financial resources and this idea would be very well received in the company, because that way, just a phone call to the user and in a few seconds giving correct instructions, he would be able to recreate your image again with all applications and customizations without a USB or any device to do this.

I apologize for the delay. I made some adjustments and managed to make it work, thank you very much!

In a task sequence, would this be applied before or after the "Apply Operating System Image" ?

It would be much more useful if you could share the script here if you succeeded!

Update: I put this in the SMSTSPostAction field: START powershell.exe -ExecutionPolicy ByPass -WindowStyle Hidden -File "C:\TEMP\install.ps1" And inside the .ps1 file there is this: Start-Process -NoNewWindow -Wait -FilePath "C:\TEMP\setup64.exe" -ArgumentList "/s" -PassThru Remove-Item -path C:\TEMP -Force -Recurse -ErrorAction SilentlyContinue Remove-Item -path C:\_SMSTaskSequence -Force -Recurse -ErrorAction SilentlyContinue Restart-Computer However you are not installing, do not delete the folders also just restart the computer at the end, any help?

The problem with that is that I don’t know ANYTHING, nor how to implement it, I’ll spend a lot of time (which I don’t have) to study the documentation, while the script, just insert it in the fields and it’s ready, and in the next version of the system image, I’ll have time to be able to put this tool into practice. Is it more complex to do the scrtipt than to use this tool? I even joined some lines but it is not working. Edit: I downloaded the tool, for me it is absurdly complex to study this now, because the image I am making is ready (using the Batch File, however the CMD.exe window keeps appearing during the login screen) I just wanted to switch to powershell.

I need to install Symantec Endpoint Protection, what would the command line be like in powershell where I can call a .ps1 script in a completely hidden and silent way? I did a previous TS that copies the setup64.exe from SEP to "C:\TEMP\" I don't have much knowledge on powerhsell as would the script that would install it silently? the argument for installing it via Batch File is / s. However, the CMD window appears during Windows logon, and Powershell can do all of this without any windows appearing, and I wanted powershell to wait for the installation to finish (I researched this and think the parameter is -WaitProcess but I don't know where how to put it) and after the installation is finished, delete the TEMP folder and restart the computer. Any help with that please?