MSMG ToolKit

MSMG ToolKit - Integrate Remote Desktop Protocol (RDP) 8.0 & 8.1

MSMG ToolKit - Integrate Remote Desktop Protocol (RDP) 8.0 & 8.1
I want to integrate this.
But it is looking for the language pack file.
I don't need a language pack!

 

How did you duplicate the explorer status bar? hehehehe

you can delete these code lines.

Code:

:: Checking whether Remote Desktop Protocol (RDP) 8.0 & 8.1 Pack file exist
if not exist "%RDP81%\Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~%PackageArchitecture%.cab" (
   echo.Remote Desktop Protocol ^(RDP^) 8.0 ^& 8.1 Pack folder is missing the below file...
   echo.
   echo."Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~%PackageArchitecture%.cab"
   echo.
   echo.Please copy the above file to ^<Packs\RDP81^> folder...
   goto :Stop
)

Code:

       echo.-------------------------------------------------------------------------------
       echo.Integrating Remote Desktop Protocol ^(RDP^) 8.0 ^& 8.1 Prerequisite Package...
       echo.-------------------------------------------------------------------------------
       call :AddPackage "%InstallMount%\%%i", "%RDP81%\Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~%PackageArchitecture%.cab"

Maybe its is needed for en-US too. Give a try.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

This may be a dumb question, but when I run the first 2 commands on a win 11 iso, I get "c:/sam/desktop/ not an executable file".!! then I get failed loading ISO!
This happens on an SSD win 10 system, but not on other systems. It seems to be looking at the PATH on the system!

 

Open the batch file and find the same lines right above/below that error message or something why it gives you that MSG.. See why it wanna use that path, unless you actually use that path

The path shouuld bbe somethin C:\Users\Sam\Desktop.

 

Thanks tcntad. I figured it out. It "toolkit" had a problem with the name of the folder I had it in!! All I did was rename the folder it ran just fine! Is that weird?

 

Put the Toolkit in the short path possible, like C:\TK.

For you may still have problems when you are in the component removal step.

This, about the short path, is recommended in the main post.

 

Does anybody know if @MSMG is okay? I see he hasn't posted for sometime and I worry that this project will be abandoned.

 

These are festive and restless times.
I hope it's just that.

Hopefully everything is fine with him and his family.

 

He is ok . fitt n fine . i think is taking rest these days

 

I really miss him.
He more than deserves a break, hoping he is OK and in good health.

Cheers.

 

Thanks for the come back. I did a short path=C: and it works great now.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I have tested with 1904x.1415 any SKU & worked perfectly at my side removing component packages via msmg toolkit 12.0 downloaded from his mega account with toolkit cmd timestamp 3rd dec 2021.

 

You need to login to view this posts content.

 

I don't know if anyone reported this yet but the latest version still has a problem integrating WMF and WPD into Win 10 Pro N which probably because ProessionalN should be ProfessionalN

 

Grateful for feedback.

That was my fault!

There are 3 occurrences of this error.

@MSMG, as this was a suggestion of mine, this should be corrected in the Toolkit official as well.

All from:
Proessional
to:
Professional

 

You need to login to view this posts content.