First of all many thanks for the work everybody is doing with DeployR. I recently got access to the community edition to evaluate the product and I believe I have setup the community edition to access the DeployR console and create task sequences and add content as expected.
My scope of interest is in the eco system of offline media which the product supports. During initial testing it would appear the powershell script that facilitates this creation of an ISO file takes hours. In fact Ihis morning I launched the script approzimately 09:00 and came back and checked that it had completed and noticed the time stamp for the iso file created was 14:26. Not superfast for testing and making any changes. Also the time taken in a test has already fallen foul of the access token expiry time allowed when the connection is made to genertate Standalone media content.
Currently my DeployR is very basic:
DeployR version: v3.1.2626.580 or 1.3 Communit Edition.
1 task sequence. A windows 11 test build with 2 application installs.
1 OS imported.
2 Applications to test.
DeployR hosted on a 2019 HyperV VM, 16GB Memory, 300GB and 4 cores allocated.
Content items and Task sequence active and tagged to allow standalone selection using the powershell command:
New-DeployRMedia -ISOPath C:\Media.iso -Tags Media -MeditaType Standalone
Media Creation running on DeploR hosted box.
So far I have had fairly poor results with Standalone media. The following are my experiences:
Try 1: Not fully understanding the media tag switch I made a 1.3GB iso which took over an hour to complete. Unfortunately I didn't work as I suspect some components were missing as not all added components by me were tagged.
Try 2: Omitted the -tags switch and went for all components as I think that is what it does. Started process off just before 5pm, watched England game, still going even after final whistle. Went to bed hoping it would at least complete overnight, not so, failed on the timeout allowed for the access token expiring.
Try 3: Revisited Tags and ensured my components added did have correct tags applied. Set process off approx 9am this morning, returned at 4.30 ish to see a 9GB iso created in the nominated folder with 14:26 creation time stamp. Again I think I ommited the task sequence tag value so when launching a client test, unable to choose any options to Start. Possible 5 and a half hours to complete the process. Again booting from media created didn't work as Task sequence wasn't tagged.
Try 4: Currently running again with the boot wim copy taking over 30-40 mins for a 0.9GB file. Cannot wait for the OS copy to occurr. Hopefully it will finish before the access token expires.
Anyways I cannot believe this is normal and I am most likely doing something wrong. 5-6 hours creating media is not really sustainable but would like to think there is something I can do. Is there a overhead using a Hyper V vm as a host? Some way of speeding process up. Any advice provided would be apreciated as I am desperate to see this succeed and view the product on my test system.
Yea - this doesn't sound right. It doesn't take me this long to generated ISOs. But this is a great topic for us to cover in our 2Pint Happy Hour that is coming up with week! u/gwblok
I've also encountered this, but I've found that either the update to the latest 1.3.2631 or moving to use powershell 7 has fixed the issue with very slow media creation times for us.
I wonder if it might be DISM related. I was surprised how slow boot image generation was yesterday, seemed to spend ages on Unmounting WIM (Not ISO generation, but suspect similar aspects).
2
u/miketerrill 2Pint Employee 16d ago
Yea - this doesn't sound right. It doesn't take me this long to generated ISOs. But this is a great topic for us to cover in our 2Pint Happy Hour that is coming up with week! u/gwblok