ZombieKiller

For the last day or so we have not been able to submit a support ticket. Whenever we click the submit ticket, we get the error "we are experiencing technical issues at the moment. please try again in a few minutes." We have tried different browsers, different computers, different networks...nothing has worked. No idea if it is our account or if it is omnissa having issues. It's quite important for us though to submit the issue we are having.

Well, there's your problem. It's McAfee. Get rid of that POS software and it will run just fine.

What is the best method of deploying out the M365 suite these days? Is it still uploading the massive bundle as a zip file and deploying it that way following this doc: https://docs.omnissa.com/bundle/SoftwareDistributionManagementVSaaS/page/DeployyourOffice365ProPluswithWorkspaceONEUEMusingSoftwareDistribution.html? Deploy using the Enterprise App Repository?

Yep, it does match. Like I said, enrollments with an x86/x64 chip, the Hub auto deploys out just fine. It's when the device has an ARM chip that it hangs. There was a known issue on this: https://kb.omnissa.com/s/article/93527 that was supposedly fixed on the 2308 console. And at least IMO it has come back.

Except that until the Hub makes it onto the device and is installed, nothing is deployed from the console. So, even if I manually upload the Hub for deployment, since the Hub isn't deployed during enrollment, it won't go out. It's a chicken and egg problem.

Anyone know of a gui tool to create a custom windows 11 start menu for deployment during OOBE enrollment? Seems the custom start menu is more involved than with previous versions of windows and I'd rather not create both a json and xml.

During a windows autopilot OOBE enrollment, the Hub should auto deploy from the console. That has always worked fine for an x86/x64 bit version of windows. Now with the Arm version of windows, I'm finding no matter what console I try this on, the Hub won't deploy and it just stays in a "pending hub" state and the enrollment doesn't finish. If I grab the arm version from getws1.com or getwsone.com and manually install it, everything finishes up just fine. Any idea why?

I don't mind manually moving them somewhere after I am done with my session with the app, I just wish it didn't save it there at all.

Stop binding your macs to AD. Apple hasn't recommended this in years. You should use something such as PSSO or even a method such as xcreds or Jamf Connect.

Use Google Santa...my favorite. https://github.com/google/santa

By default WS1 admin assist saves repackaged apps to ~\Documents\Workspace One Admin Assist. Which is not ideal because it should be asking where to save it to, such as a repository or github. Is there a way to change the default directory it saves to?

It mysteriously fixed itself after last night's monthly console maintenance. Leads me to believe whatever the issue is/was is console related and not on my server. I looked at the acc server log and it showed that the connection re-established almost exactly when I got the email when the maintenance was finished.

AirWatch.CloudMessaging.Client.AwcmClient.SendMessageRetryAsync Failed to send Idle message to AWCM: https://awcm1380.awmdm.com/awcm, Retrying: No, MessageId: 47cee096-a350-4e0f-ad74-046c4887184c, CorrelationId: , OriginId: 5c053907-a680-454d-9791-3fbc17ea1057(https://cnXXX.awmdm.com/20038/acc), DestinationId: , Exception: System.Net.WebException(ProtocolError), Message: The remote server returned an error: (401) Unauthorized. Method: AirWatch.CloudMessaging.Client.AwcmClient.SendMessageRetryAsync; 2024/08/28 14:26:58.951 UEMPROD-OMNTOOL aee0c14a-0466-4ca6-8f15-b4c96e8fdbb0 [0000000-0000000] (7) Error AirWatch.CloudMessaging.Client.AwcmClient.TryParseAuthenticationErrorFailure Error from AWCM US08PACMXXXBA1.GLOBAL.SAAS: Replay Attack; perhaps it doesn't have this AirWatch instance's Secure Channel Certificate. Method: AirWatch.CloudMessaging.Client.AwcmClient.TryParseAuthenticationErrorFailure; 2024/08/28 14:26:58.967 UEMPROD-OMNTOOL aee0c14a-0466-4ca6-8f15-b4c96e8fdbb0 [0000000-0000000] (7) Error AirWatch.CloudConnector.AccServiceListener.ListenForRequestsLoop/1 Failed to reach AWCM at https://awcmXXXX.awmdm.com/awcm Method: AirWatch.CloudConnector.AccServiceListener.ListenForRequestsLoop/1; 2024/08/28 14:26:58.967 UEMPROD-OMNTOOL aee0c14a-0466-4ca6-8f15-b4c96e8fdbb0 [0000000-0000000] (7) Error AirWatch.CloudConnector.AccServiceListener.ListenForRequestsLoop/1 ACC Listener Task faulted with state ServerReject; retrying in 2 seconds.*** EXCEPTION *** System.Net.WebException: The remote server returned an error: (401) Unauthorized. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at AirWatch.CloudMessaging.Client.AwcmClient.<SendMessageRetryAsync>d__72.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at AirWatch.CloudMessaging.Client.AwcmClient.<ListenForMessagesAsync>d__65.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at AirWatch.CloudConnector.AccServiceListener.<ListenForRequestsLoopAsync>d__15.MoveNext()Diagnostics Context ******************* PID: 5136 Process Name: CloudConnector.Service Process Identity: Application Identity: anonymous ******************* The connection between my SSaaS console and my ACC has been down for days and I have no idea why. The ACC logs show that the secure channel certificate is missing, which is weird because this is SaaS and AWCM is not on-prem. I've even deployed a new VM and done a new ACC install with a new installer from the console. Same problem. I thought I would download the secure channel certificate installer from the console, but that link doesn't do anything and I cannot seem to find the installer anywhere. Any thoughts?

That was it, thank you for that.

I'm trying to create a powershell script that will register a device and then will send an enrollment email to the user. The script is set for a specific server and then prompts for info (api key, admin u/p, user info, device info). It should be using the correct api to register the device, but I keep getting a "404 not found" error. I'd love if someone had a bit, could look at it and see what I am missing. registerdevice6.ps1