User Profile
rastok
Brass Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Re: Azure sync errors - DeletingCloudOnlyObjectNotAllowed
It is strange that the Object GUID keeps changing on each sync cycle and makes it difficult to correlate. Have you tried to run idfix to find any issues? You can also try to run Get-AzureADUser | Where {$_.DirSyncEnabled -eq $null} | Set-MsolUser -ImmutableId “$null” just to set all immutables to $null.1.6KViews0likes0CommentsRe: Univeral Print Intune error - Install (User) -2147418113 & -2138701812
Hello abraxid. Yes I resolved it. It was an issue with conditional Access policy that was blocking the silent authentication. You need to look at Azure AD sign in logs, pay attention to failure and you should be able to see the app that corresponds to the Universal Print. Let me know if you need further help.8.7KViews0likes2CommentsRe: upprinterinstaller.exe pop up windows
Hello RNalivaika, I installed UP the same way you did with Intune but I have encountered an issue that not sure if you seen it before. I have posted it here instead if you might have an idea. I have an active ticket with Ms support and it has been almost two months and no solution. Here is my post https://techcommunity.microsoft.com/t5/microsoft-intune/univeral-print-intune-error-install-user-2147418113-amp/m-p/3671228#M1273111KViews0likes0CommentsUniversal Print Intune error - Install (User) -2147418113 & -2138701812
I'm currently doing a PoC on Universal Print using connector installed on an on-premise server 2022. I successfully installed the printers on the Connector server, registered with Azure UP (Universal Printer), shared it and began configuring Intune (MEM) to deploy on Win 10 machines. I used printer provisioning from the configuration profile catalog and put all the required values. I targeted the profile on a group of users. The results were interesting. Two users installed the UP with no errors, 3 other users failed to install with error message details below. I could not find any of these errors documented any where. I have engaged MS Support and waiting on solution. These errors are not documented anywhere for MEM. Here are the errors in anyone might be able to help Install (User) -2147418113 Install (User) -2138701812 I have also attached screenshot from MEM3.3KViews0likes2CommentsUniveral Print Intune error - Install (User) -2147418113 & -2138701812
I'm currently doing a PoC on Universal Print using connector installed on an on-premise server 2022. I successfully installed the printers on the Connector server, registered with Azure UP (Universal Printer), shared it and began configuring Intune (MEM) to deploy on Win 10 machines. I used printer provisioning from the configuration profile catalog and put all the required values. I targeted the profile on a group of users. The results were interesting. Two users installed the UP with no errors, 3 other users failed to install with error message details below. I could not find any of these errors documented any where. I have engaged MS Support and waiting on solution. These errors are not documented anywhere for MEM. Here are the errors in anyone might be able to help Install (User) -2147418113 Install (User) -213870181211KViews0likes8CommentsRe: Not able to start Azure Cloud Shell
Prerequisite for launching a Cloud Shell is a Storage account and File Share that would be mounted to your session. Is this the first time you encountered the error? It appears as if you were once successful then there was no activity causing the the timeout. By design, the cloud shell session is reset after 20 min of no activity. What happens if you select quit or reconnect? when you were connecting to the shell, you must have been prompted to use existing storage account and File share or create a new one. Also look at storage accounts in your subscription and try to identify the one that is associated with the cloud shell.2.8KViews0likes0CommentsRe: VirtualMachineScaleSets and ZonalAllocationFailed
The most common cause of this issue is limited compute capacity on the cluster /host in which your VM scale set is deployed. Any incident that causes your VM to be deallocated get exposed to a risk of not starting if the host cluster is bordering on being maxed out. Your VM became unlucky and most likely someone else VM which was off was started when yours was deallocated and therefore took over your resources. The fastest way to get your VM is to resize it to another SKU either upwards or downwards and attempt to start the VM. It is very unlikely that all the SKUs are used up. If that does not work, take the VM snapshot then a disk from it and then create another VM and add to the same cluster, I'm not 100% sure but might place this new VM on a different host or different cluster with the same SKU you originally had. My thoughts: This is unfair situation to a customer with critical workloads in the VM. I think Microsoft product team should take this feedback and enable capacity monitoring on clusters. The customer should never be the first to find out that the cluster is full, after all the more VMs running, the better is the look of the Ms bottom line:)1KViews1like0CommentsRe: Azure Virtual Desktop - Best practice for spanning an environment across multiple subscriptions
Hello, 1. Design you’re a landing zone - put all subscriptions under one roof by leveraging management groups if you own them all. Other option is to build vnet peerings between subscriptions 2. Collect both business and technical requirements 2. Use workshops with stakeholders to showcase the future state of the environment then use it's outcome to design the final solutions (principle: design before you build else someone may ask: what are you building?) . The design should cover all stated requirements including the need to establish a hub and spoke topology in order for you to utilize all the subscriptions you mentioned for whatever resources you want to deploy in them. note: If you don't want to maintain domain controllers as VMs, with a budget of about $150/Mo, you can spin out an Azure AD Domain services which is a platform and has build in redundancy.1.4KViews0likes0CommentsRe: Azure AD Risky User license requirements?
All users need P2 in order for you to gather and analyze risky user logs. Please also note that all logs are collected even with P1 license but logs that require P2 visibility will be listed as "Other detected risks", just paraphrasing. You will not be able to drill into it but you will notice existence of more risk detections.6.6KViews0likes2CommentsRe: Azure AD Risky User license requirements?
As a global administrator or any administrator with Azure AD, you don’t require a license to perform any administrative tasks within the role such as user creation, license assignment and so is the setup of Azure AD Risky users / Sign ins and email alerts. It is the role you require and not the license. If you want to verify this on the tenant: 1. Create a user P1 and assign global admin role - assign Azure AD P1 license 2. Create a user P2 and assign global admin role - assign Azure AD P2 license 3. Create a user P3 and assign global admin role – Do not assign any license 4. Sign into each user account in step 1 – 3 and attempt to perform any tasks like those you stated – make observations6.5KViews0likes0CommentsRe: Announcing General Availability of Scheduled Agent Updates on Azure Virtual Desktop
Is the agent self-updating removed moving forward? This has been a huge pain for older versions of the agent as well as SxS when updates occurs but then it hangs and breaks the session host. Otherwise this control is highly welcomed.3.2KViews1like1Comment
Recent Blog Articles
No content to show