Josh Levitsky

As an update we are still on schedule for the first customers to get 14.9.0 on Wednesday next week. An email will be going out to them as soon as the KB articles are live. This KB + Emails are planned for Monday (Nov 7th) morning. You'd only see an email if you are in that first round. The wider release is planned for the beginning of the week after.

As an update we are still on schedule for the first customers to get 14.9.0 on Wednesday next week. An email will be going out to them as soon as the KB articles are live. This KB + Emails are planned for Monday (Nov 7th) morning. You'd only see an email if you are in that first round. The wider release is planned for the beginning of the week after.

A couple of customers have asked about https://nvd.nist.gov/vuln/detail/CVE-2022-3602 that was disclosed yesterday. We had been waiting for the update to be available in order to roll it in to FileWave. As previously mentioned, the current release plan is for FileWave 14.9.0 to go next week to the first customers, and the following week to everyone else. The time between now and next week is needed for QA to ensure that there are no critical bugs that slip through.

From PS I don't think we have anything already made. There are articles like: https://devblogs.microsoft.com/scripting/use-powershell-to-enable-wi-fi/ that talk about how you could enable it with PowerShell. If you take that idea and combine it with the idea in the attached fileset of a Requirement Script that would keep on knocking WiFi back to enabled then that may give you what you want. The script in the attached example is actually just a batch file that kills Microsoft Edge and then does an exit 1. It could easily be PowerShell instead. This will run every 2 minutes; taskkill /im msedge.exe /f exit 1 Another approach might be to use a blocker script. When you click the toolbar to make a New Desktop Fileset then you would click Policy as the type of Fileset. If you go this route then every 5 minutes would be the interval, and you could make a Blocker Script that handles a variety of things you want to enforce on your clients. Use caution here because your script must exit with 0 or else that tells the FileWave client to basically lock the client. I'm very curious what other customers have done to solve for your specific question and maybe they can share an example that specifically gets to what you are trying to do. I did also look through the Windows Profiles available with Windows MDM and there isn't a profile setting available within that to prevent disabling WiFi. Block Microsoft Edge.fileset.zip

One thing to check is that your SSL cert is good. For example I can go to https://fwjoshlab.filewave.net:20443 in a browser and see that there is no complaint about SSL. I believe I saw what you show the other day when someone had a revoked SSL cert on their server. If it was the SSL cert. Below is where SSL certs are updated in preferences. Note that if your SSL cert was revoked by someone in your organization that the Expiration Date may not have passed, but if you try to go to your server in a browser (as in my example of my server's URL) then that's usually a good indicator of if the certificate is good or not. Beyond that unless you see someone post another idea it may be good to start up a request with support via help@filewave.com or https://help.filewave.com

Did the problem start this week by chance and worked before? Have you logged in to Apple Business or Apple School Manager and accepted the new terms and conditions that posted on Monday? Just wanted to eliminate that simple solution first and confirm if enrolling ever worked for you or just broke on Monday?

Hi @AnEngelsen I don't yet have that KB posted, but here's the concept; Custom Field - I use a string for this where the field is first set to "new" and then "one" and then "two" to flip/flop devices between 2 smart groups Attached: Elevate Admin Custom Fields.customfields.zip Smart Groups - I have 2 smart groups as seen below. They are set to toggle devices between them based on if the field is set Below is what the "1" smart group looks like. The "2" smart group is the same but looks for a value of "one" on the custom field. Associations - Next you need the stuff you want to send. In my case I have the same Fileset twice. I duplicated it. I associated the first to the "1" smart group and then the "2" to the second smart group. I made them be Kiosk associations so that they wouldn't run over and over. This is meant for a tool that you want to have always available to run. Elevate Permissions (macOS) 1.fileset.zip Elevate Permissions (macOS) 2.fileset.zip Perhaps take a look at what I have so far and if anyone wants to make this fancier or address any flaws in it I'm happy to get feedback. I also had a framework for a Windows version but it was lost when I made a silly mistake. It basically did the same thing as this macOS Fileset did, but for Windows. I know this is not a perfect solution but it was what I came up with to overcome our lack of a Kiosk option to re-run something.

We've been working out the release timeline for FileWave 14.9.0 and our current plan is that the week of November 7th it would go to the first wave of customers. That's where you can ask if you like to be amongst the first. That week @Emma Ainsworth, @Andrew Kloosterhuis and I will be at HECC in Indiana and will have a session on the Friday morning to talk about the release some with anyone at that conference. The week of November 14th would then be the release to all customers which would also be the week of our next Alliance eMeeting so we'd be able to talk about the release with anyone globally who would attend that virtual event. We also post that to our YouTube channel afterwards so there will be another opportunity to see it. As always these timelines are subject to change if we find a critical issue, and I can post here if I find that it changes.

Thanks for mentioning that. I'll have to take a look at if there's a way to avoid the persistent person who launches it, leaves the dialog up, and launches again. We can look to improve that.

No problem. First we have our links to our Roadmaps here: https://fwkb.atlassian.net/wiki/spaces/KB/pages/4333256/FileWave+Product+Management and you can also make product suggestions and vote on things. The links go to the Foundry which you can get to since you can sign in here on the Alliance Forums. Specifically for 14.9 it's in QA now and they are working on checking that it passes all the tests. I can't give a specific date but say that we are working towards a couple of weeks to get everything clear. This version will include a tool to move from Associations to Deployments that was shown off on the WebAdmin Webinars. I'd say as soon as there is a build where we feel it's able to have a selected date I could share then. Also if anyone wants to be amongst the first to get releases we do them in waves so no matter if you are on-premise or hosted by us just let me know at josh.levitsky@filewave.com and we can make new releases available sooner to those who ask to be on the list.

@cdegaeta You should see an email shortly... We are as happy as you are to see Apple have released iPadOS 16.1 and macOS 13 Ventura for general distribution, and we are excited to deliver support for them. Here's what you can expect from FileWave regarding these releases: Version 14.8.0 currently supports both Ventura and iPadOS 16.1 from a management and content distribution perspective Version 14.9 is on its way soon with support for the new Apple features/profiles, with some more FileWave goodies besides. If you have questions about this topic, please join us on the Alliance Forums. The forum uses our Single Sign On like the Foundry and Support sites. If you have trouble logging in, please reach out to Customer Experience.

Hi John, So for an existing Payload (known as Fileset in Native) you can click on the Payload and then on the bottom right click Edit and it'll look like my image below. You can then make changes. On the top right you'll see an up and down arrow set of icons. These are import and export. So you can make a new Payload or open an existing one and pull in a .mobileconfig file via the import. Let me know if this doesn't answer what you are looking to do.

I was curious if folks have tried ChromeOS Flex and if you have the FileWave extension present and reporting? Any success stories or things that you got stuck on? Flex just seems to be ChromeOS but for non-Google hardware so I would think everything is very normal as compared to ChromeOS on Google hardware.

While I don't know that I have an answer (and perhaps another customer will) I did see this https://success.trendmicro.com/dcx/s/solution/000277823?language=en_US and was wondering if the profiles published there are helpful. They also show FileWave specific info. I didn't get to dig in to this but was hoping maybe that would be helpful. It's also important to make sure the profile hits the device before the software does or likely you'll get prompted still since Apple devices like these profiles to be present before the app launches.

This has come up a few times recently so @Andrew Kloosterhuis made a KB article to show how you can make a WebClip that opens Chrome rather than Safari. https://fwkb.atlassian.net/wiki/spaces/KB/pages/70352897/Creating+Web+Clip+URL+links+to+open+with+Google+Chrome+on+iOS+iPadOS

Anyone thinking about Ventura coming out shortly may want to also consider this thread: https://alliance.filewave.com/topic/41-macos-ventura-blocking/#comment-110 If you don't consider it then think about if you'll suddenly have devices on Ventura when it releases. It's hard to know until it's really out but if you have AppleSeed, a developer account, or the public betas you could do independent testing to confirm if you feel comfortable with being able to block the update until you can verify that you have no compatibility issues with applications.

Just curious if folks have been looking at how to block Ventura upgrades from earlier OS versions? This is on GitHub: https://github.com/Theile/venturablocker In the FW KB: https://fwkb.atlassian.net/wiki/spaces/KB/pages/4329971/macOS+-+Block+Apple+Install+macOS+Application The FileWave KB article worked for Monterey, Big Sur and prior. I haven't been able to test it for Ventura but wanted to get a thread going so people could consider if you are going to block it, and how you are going to block it if you know you have certain apps that aren't yet compatible since it's just around the corner.

Apple has policies that prevent us from saying we support it before it is released. As soon as it is released we will be able to say. As soon as it and iPadOS 6.1 come out we will be able to say.

My understanding is that this change is so that the boosters don't all present themselves to the server or other boosters as "FileWave NATS Booster" so it would apply.

I'm not sure that there is a restriction that exists yet for that from Apple. If I see something or if someone else does maybe they can add to this thread. -Josh

By default I believe every 24 hours the FW server sends a push notification to try and get updated info from the device, but also when something is associated with it or a command is sent to it then an APNS push will happen. If you pick an iPad and double click it in the Clients window to look at the details like in the below image and go to "Command History" it'll show you the APNS pushes and if they were sent and if they were received by the device. You should see ones from today and if you stay on the window you should see them change to sent and then acknowledged if the device is on the Internet and can reach both Apple and your FileWave server. If you aren't seeing the commands acknowledged then there is either a communication/firewall issue or it can be an issue with your FileWave server to work out with Support possibly.

I think in iOS 15 this became a thing and we do have in Profiles.... Let me know if I'm wrong, but I believe "Allow password sharing" is the restriction you want to set. You'd want it not checked so that it wouldn't be allowed. This image comes from a FileWave 14.8.0 server.

I've been traveling and haven't gotten to set it up, but have been reading up on it to see it it could solve this need. It feels like it may be a good solution. It's free with the option to pay for support which is a nice model to see how it works and then pay for support to support them and be able to get help. I'm hoping that if I can see it work or find a customer who has it figured out maybe we can all help one another and I'll put it in the Knowledge Base. It feels like this is a good solution.

Thanks on that. I was thinking that the 2 minute default tickle would play a part in this and devices realizing something changed. It's one reason I might make the tickle a larger number to have things seen after a bigger interval than 2 minutes but also at the same time that short interval means when you make a correction it'll be seen quickly too. What PN mentioned about using the API to send a verify would be a way to ask the devices to do things like update custom fields and all the many things that happen every 24 hours in a normal verify but quickly. In your case the 2 minute tickle I think made things happen quickly because detecting a model update is in the tickle.

Hi @sean_a can I ask why you want them to do it? Is it because you are doing something to all your devices outside of filewave like upgrading all their RAM and you want the inventory to be updated sooner? Or is there an issue where the inventory seems wrong for some devices? I ask because clients will do a Verify every 24 hours so the data in theory should become correct fairly quick, but I wasn't sure of the motivation to do it which might make the answer better. -Josh