We've been unable to configure this via CSP,
Even if we could get firewall rules working by CSP this would be an important step over the current situation.
The following is from:
"I opened a ticket to Azure support (REG:118083118906763) and after 2 months of escalations they stated this does not work on Intune:
“Basically, the capability of enabling a rule in Firewall that will enable a port such as TCP 3389 using custom policies is not currently possible using a CSP. There, just, aren’t any CSPs currently available to allow ports in Windows Firewall.”"
22 votesAnonymous shared this idea ·
Thanks for the comments, just a few questions to the gallery.
What platform is this issue with. I’m only seeing IOS devices in your comments, so wanted to double check.
Also, are you having this issue with shared devices or just re-deployment? Unclear from all the comments. Do you want to keep all installed apps on the devices? Depending on your platform, you should be able to already do this for shared devices.
Windows devices please.
As of the week of August 27, you can use a template to control how the machine will be automatically named. So not exactly static, but gets you away from total random. From the discussion, sounds like not total random was good enough for some, but not all, so I will switch this back to “noted”.
more detail about what we released in August:
When you create an autopilot deployment profile, you can designate a name, which must be 15 characters or less, and can contain letters, numbers, and hyphens. Names can’t be all numbers. Use the SERIAL macro to add a hardware-specific serial number. Alternatively, use the RAND:x macro to add a random string of numbers, where x equals the number of digits to add.
It’s only available with the Windows Insider build for now.
This would be very useful to have the device pick up a desired name during enrollment or self provisioning.