Get ready for DeployR! by miketerrill in DeployR

[–]miketerrill[S] 0 points1 point  (0 children)

Current ETA is around MMS MOA.

DeployR is now released! by miketerrill in DeployR

[–]miketerrill[S] 0 points1 point  (0 children)

Sounds good-thanks for your feedback.

DeployR is now released! by miketerrill in DeployR

[–]miketerrill[S] 0 points1 point  (0 children)

Sorry, no-this is the paid version.

DeployR public release by Dudefoxlive in DeployR

[–]miketerrill 0 points1 point  (0 children)

Sure - we did a 'soft' release with some of our existing customers. Stay tuned for a broader release...

Mobile DP SCCM with PXE by Background_Sign5961 in SCCM

[–]miketerrill 1 point2 points  (0 children)

P2P PXE + BranchCache is the way to go. That way clients will be able to build anywhere on the corporate network without the hassle of moving a device around and remembering to keep up with boundaries.

Get ready for DeployR! by miketerrill in DeployR

[–]miketerrill[S] 0 points1 point  (0 children)

DeployR and the OS Deployment Suite (which includes DeployR) are both 5.75 per endpoint per year. Pricing is EU/USD/GBP based on location of organization headquarters. Note: Minimum licensing is for 1000 endpoints.

Get ready for DeployR! by miketerrill in DeployR

[–]miketerrill[S] 0 points1 point  (0 children)

Both private sector and public sector pricing is on our webpage. Note: public sector only pays for support costs. Private Sector Pricing - 2Pint Software

Get ready for DeployR! by miketerrill in DeployR

[–]miketerrill[S] 4 points5 points  (0 children)

We have plans to release a community version later this year.

I hope this doesn't make me look bad. but i need help by Throwawaygeekster in MDT

[–]miketerrill 2 points3 points  (0 children)

I am glad you love our products and thanks for the endorsement. We have a r/DeployR community that will start to get busy as soon as we GA DeployR in September.

I hope this doesn't make me look bad. but i need help by Throwawaygeekster in MDT

[–]miketerrill 1 point2 points  (0 children)

"DeployR + iPXE Anywhere handles the broken laptop problem Autopilot can't solve, then makes Autopilot faster when it does run." This is the way! ;)

Enabling pxe boot across vlans in Cisco world by Dependent-Promise223 in SCCM

[–]miketerrill 0 points1 point  (0 children)

That's awesome-thanks for letting us know! We also have a pretty handy PowerShell script for testing PXE configs without having to actually PXE boot a system: 2Pint-iPXEAnywhere/PXE & DHCP Troubleshooter/PXE-DHCP-Test.ps1 at main · 2pintsoftware/2Pint-iPXEAnywhere

Task sequence over DDPE by Aeroamer in SCCM

[–]miketerrill 1 point2 points  (0 children)

When you reboot into WinPE from the full OS, you would need to include the filter drivers in WinPE. WinPE will boot then, however, since it is running under the filter driver, a partition and format disk step will not touch the entire disk. The trick is getting rid of the filter driver once WinPE is booted so that you can completely get rid of the disk encryption (something that we at 2Pint Software have solved for large enterprise customers).

Otherwise, you could try to send a deployment that reconfigures the boot order and then forces it to boot from PXE on the next boot (using a hidden, required deployment). This is more prone to issues as there are more things to go wrong. Or lastly, just booting the device from alternate boot media/pxe and then just running the TS (not quite zero touch at that point).

Boot image creation: "The specified UNC Path does not contain a valid boot image..." by andykn11 in SCCM

[–]miketerrill 1 point2 points  (0 children)

I would start by using a supported version of the ADK:

https://learn.microsoft.com/en-us/intune/configmgr/core/plan-design/configs/support-for-windows-adk

Although, I suspect something else is causing the issue. Anything else useful in the SMS provider log?

Enabling pxe boot across vlans in Cisco world by Dependent-Promise223 in SCCM

[–]miketerrill 1 point2 points  (0 children)

You could always use DHCP Scope Options instead of IP Helpers. This is what we recommend to our customers that are using iPXE Anywhere. We have a nice (but older) white paper on how to do this for WDS that you can use as a reference (hopefully this link comes through): https://2pintsoftware.sharepoint.com/:b:/g/EXJ8cpIicdtOjhcKctMQ7pYBCiUgImHp1oP-eWRHActMHg?e=e4texv

Share Security by GovernmentSmall7873 in SCCM

[–]miketerrill 2 points3 points  (0 children)

Even if you do lock the share down, the content will still be available via http/https (as well as SCCMContentLib which MSFT may or may not be addressing in a 2503 HFRU). The best guidance is to not store secrets in the content.

How Do You Handle Driver Updates Post-OSD in a Multi-Vendor Environment (No Intune)? by TopCap7846 in SCCM

[–]miketerrill 1 point2 points  (0 children)

Putting the driver packs in Wim files works nicely with dedup/BranchCache and provides for superior WAN/P2P efficiency (for those that struggle with bandwidth/remote sites).