anyweb

i'm not sure which app you mean, but perhaps you mean this ? https://aka.ms/mfasetup and in there the USER can change to whatever default method they want, this is a user setting and we cannot enforce it (that I am aware of)

where did they change the option, at the login to windows screen or somewhere else ?

was this question related to Windows 365 or Azure AD ? number matching will be the default method come february 2023, so how can users choose something else ? Can I opt out of number matching? Yes, currently you can disable number matching. We highly recommend that you enable number matching for all users in your tenant to protect yourself from MFA fatigue attacks. Microsoft will enable number matching for all tenants by Feb 27, 2023. After protection is enabled by default, users can't opt out of number matching in Microsoft Authenticator push notifications.

Introduction While trying to connect to my Windows 365 Cloud PC using the Remote Desktop app, I got the following error. as shown here clicking on See details revealed some more info. I double checked using the Windows 365 App and it too, produced the same error code. Your connection failed. Error Code: 0x3000047 A guick google revealed similar error codes for AVD (Azure Virtual Desktop) but nothing for Windows 365. And the problem didn’t match my suspected issue. As this Cloud PC is Hybrid Azure AD joined to my lab, I suspected that my external internet facing IP address has changed or access to Routing and Remote Access Server (RRAS) was not working. Logging in to my RRAS server I could see this. checking in Azure, I could clearly see that the the Hybrid Azure AD VPN connection was listed as not connected, and again I suspected that it was due to my external internet facing IP address having changed (it changes often with my current ISP). On my RRAS server I checked my external internet facing IP address using one of the many websites out there to determine your IP address, and it had indeed changed. With the new IP address, I changed the settings in Azure for my Windows 365 Hybrid Local Network Gateway and then clicked on Save. Back on the RRAS server, in routing and remote access, I tried to Connect to the VPN again… and this time it worked ! and after trying the Windows 365 App again, it connected just fine ! problem solved

Welcome Austin, i've never heard of Dark Basic, what is it ?

I contacted Johan and here's his reply Hmm, I have actually done this once.... He will have to run a ds-Query against Global Catalog, as opposed to Ldap..... Or pay me to give him a custom TSCommander, including him signing a paper that he's responsible for not having several computers with the same samAccountName in multiple Domains

why do you tink you need a reboot ? just add a rescan to your diskpart script...

hi, i assume you mean this post if you try the net use commands manually what is the output ?

Introduction I recently presented a session with Paul Winstanley in a USA Windows 365 User Group meetup focused on all things Windows 365. The meetup included some great ‘what’s new’ content from Microsoft Program Manager Christiaan Brinkhoff and some great Powershell/Graph automation information and demos from Dawn Hertz. Myself and Paul then did a session about Windows 365 Hybrid Azure AD join which is one of the parts of our current series all about getting started with Windows 365 here. The video is now up on youtube and you can review it here. Our session starts at the 1:20 mark here: do us a favor and check it out, oh and do check out our series too ! Below you can find all parts in this series: Getting started with Windows 365 – Part 1. Introduction Getting started with Windows 365 – Part 2. Provisioning an Azure Ad Joined Cloud PC Getting started with Windows 365 – Part 3. Provisioning a Hybrid Azure Ad Joined Cloud PC Getting started with Windows 365 – Part 4. Connecting to your Cloud PC Getting started with Windows 365 – Part 5. Managing your Cloud PC Getting started with Windows 365 – Part 6. Point in time restore Getting started with Windows 365 – Part 7. Windows 365 boot Getting started with Windows 365 – Part 8. Windows 365 switch Getting started with Windows 365 – Part 9. Windows 365 offline Getting started with Windows 365 – Part 10. Patching your Cloud PCs with Windows Autopatch cheers niall

the machine account (cm01$ or whatever your site system account is) can install the roles, add the machine account to the local administrators group on that site server but on my lab server(s) I always define boundaries (based on ip ranges), so that would be the first thing i'd suggest you look at, even if you think you don't need them...

happy you got it working !

do you have any boundary added in your boundary group

ok we need to see the smsts.log to dig deeper, feel free to clean if of any sensitive info before attaching here

the content might be on your dp but is it the correct source version ? enable the Source Version column in your boot images to see what source version it is set to did you set boundaries correctly ?

here you go

you forgot to include the smsts*.log and app*.log files, they will show any failure.

check your pm

i need to check when i get home, i don't have them online... i'll check later tonite and ping you on pm

i'll see if i can find the files and make them available to you

dont use a task sequence, use a powershell script that runs based on events that are triggered from actions that you are interested in, such as logon, logoff etc...

Introduction This is Part 4 in a new series of guides about getting started with Windows 365. This series of guides will help you to learn all about Windows 365 in a clear and insightful way. This series is co-written by Niall & Paul, both of whom are Enterprise Mobility MVP’s with broad experience in the area of modern management. At the time of writing, Paul is a 6 times Enterprise Mobility MVP based in the UK and Niall is a 12 times Enterprise Mobility MVP based in Sweden. In this series we aim to cover everything we learn about Windows 365 and share it with you to help you to deploy it safely and securely within your own organization. In Part 1 we introduced you to Windows 365, selecting the right edition with the level of management that you need, choosing the plan that suits your users needs at a cost you can afford, or modifying the configuration to make it more suited to your individual needs, purchasing licenses and saving money for your organization via the Windows Hybrid Benefit. In Part 2 you learned how to provision an Azure Ad joined Cloud PC and take a look at the different network options available when provisioning an Azure Ad joined Cloud PC. In Part 3 you learned about the steps needed to successfully provision a Hybrid Azure Ad Joined Cloud PC. Below you can find all parts in this series: Getting started with Windows 365 - Part 1. Introduction Getting started with Windows 365 - Part 2. Provisioning an Azure Ad Joined Cloud PC Getting started with Windows 365 - Part 3. Provisioning a Hybrid Azure Ad Joined Cloud PC Getting started with Windows 365 - Part 4. Connecting to your Cloud PC <- you are here Getting started with Windows 365 - Part 5. Managing your Cloud PC Getting started with Windows 365 - Part 6. Point in time restore Getting started with Windows 365 - Part 7. Patching your Cloud PCs with Windows Autopatch Getting started with Windows 365 - Part 8. Windows 365 boot Getting started with Windows 365 - Part 9. Windows 365 switch Getting started with Windows 365 - Part 10. Windows 365 offline In this part we'll cover the following: Connections available Windows 365 app Remote desktop client Web browser Windows Installing the Remote Desktop client Subscribe to the Cloud PC Accessing remote desktop features Windows 365 app macOS Installing the Remote Desktop client Adding a workspace Accessing remote desktop features iOS (iPad/iPhone) Installing the Remote Desktop client Adding a workspace Accessing remote desktop features Android Installing the Remote Desktop client Adding a workspace Accessing remote desktop features Linux Related reading Summary Connections available At the time of writing you can connect to your Windows 365 Cloud PC using the following methods: Using the Windows 365 app (Windows 11, Windows 10 coming soon) Using a Remote Desktop client (Windows, Mac, Android, iOS) Using a HTML 5 capable web browser (Windows, Mac, Android, iOS, Linux, ChromeOS) Windows 365 app The Windows 365 app is currently Windows 11 only and available for download via the Microsoft Store. Search for Windows 365, get the app and click Open once done. In later versions of Windows 11 it'll come bundled as a built-in app and Windows 10 support is coming. The Windows 365 app was introduced during the Microsoft Ignite 2022 Keynote (by Satya Nadella) and it allows a seamless way of connecting to your Cloud PC. There's no need to copy a subscribe URL, just login and your Cloud PC is available. The app can be launched from your start menu or taskbar. For a deeper look at the Windows 365 app (which is still in preview) please click here. Currently the capabilities are not yet on par with the Remote Desktop client but we think that'll change soon. Remote desktop client If you are using Windows, macOS, Android or iOS device then there are remote desktop apps available to download for those devices. At the time of writing the Remote Desktop app is the most feature rich method of connecting to your Cloud PC but it's not without issues, for example on iOS, macOS and Android, you have to copy the subscribed URL and add that to your workspace, it's not automatic. Using the Remote desktop agent will give you the power to use multiple monitors (up to 16 with Windows/macOS) and other hardware, as detailed in the following table. Web browser To access your Cloud PC from any device using a web browser, navigate to https://windows365.microsoft.com using the credentials of a user that has been assigned a provisioned Cloud PC. Click on Open in browser to launch the connection using your web browser. Even though the web browser connection method allows you to connect to your Cloud PC from practically any device, your abilities in that session are limited. Below is a table showing redirection of various devices using different connection methods, look at what the web browser is missing compared to the remote desktop app. For example, when using a web browser, you won't have the same fine control that you have with the Remote Desktop client or via the Windows 365 app. Not only that but things like multi-media redirection or multi-monitor support or using a web camera to enable video for Teams meetings won't be an option if you choose the web browser as the method of connection. To get the most out of your Cloud PC and to use the hardware features of the computer (or tablet/phone) that you are accessing it from, you'll need to install a Remote Desktop client agent or use the Windows 365 app (currently Windows 11 only). You can see the other available connection options by clicking on the download icon shown below. The web page automatically detects the operating system you are running and highlights a suitable client agent if one exists for that operating system. Windows We've already covered the connection types available for Windows in the Connections Available section above, as Windows can handle all three connection methods with ease. To summarize, Windows can connect to Cloud PCs using Windows 365 app (Windows 11 currently, but Windows 10 coming soon) Remote Desktop client Web browser Installing the Remote Desktop client To install the Remote Desktop client for Windows, go to https://windows365.microsoft.com, click on the download icon and select the download for the architecture matching your version of Windows. That will allow you to install the Remote Desktop client. Subscribe to the Cloud PC Once installed you'll need to Subscribe to your Cloud PC. To do that, click Subscribe and enter your Cloud PC credentials. Once you have subscribed to your workspace, your Cloud PC will be listed in the Remote Desktop client. Note: It is also possible to also add the feed URL to a "_msradc" DNS entry to automate the feed discovery for a domain. See the following for more info. Thanks to @novafunction Accessing remote desktop features You can configure settings by right clicking the Cloud PC. You'll get access to settings allowing you to (for example) configure multiple monitors. Multiple monitors are great with Windows 365 (up to 16 supported with Windows/macOS) Windows 365 app If you want the easiest/seamless experience, go for the Windows 365 app but keep in mind that it's still in preview at the time of writing so is subject to change. For an in-depth look at the Windows 365 app (which is still in preview) please click here. macOS Apple's macOS computers are very popular indeed especially with the Apple silicon (M1/M2) chipset. There are two options of connecting to your Cloud PCs from macOS, by using a web browser session or via the Remote Desktop client. Note that web browser session lacks the same abilities as the Remote Desktop client. To access the web browser session, simply open your web browser to https://windows365.microsoft.com and login using the credentials of a user that is licensed to use a provisioned Cloud PC. Installing the Remote Desktop client The Remote Desktop client is available in the Mac App Store. To easily find the download, click on the download link and you'll see the Microsoft Remote Desktop for Mac download link. It will be highlighted as shown in the screenshot below. click on Go to Mac App Store and get the app. The Microsoft Remote Desktop app will launch after installation is complete. Adding a workspace After the app is installed, you'll need to add a workspace. To do that, go back to the web browser session and copy the subscription URL. Then in the app click on the + drop down menu and select Add Workspace. paste in the subscription URL and enter your Windows 365 Cloud PC credentials when prompted. Once done adding the workspace your Cloud PC will be listed in the app. Accessing remote desktop features To access or change the Remote Desktop app features, you'll need to right click the Cloud PC icon in the app (2 fingers on the touch pad). This brings up a drop-down menu with 2 options Connect Edit Select Edit to review or change the connection settings. Next, place a check mark in the box beside your Cloud PC name (by default it's not checked). and this brings up the settings you want to see/change. For example, to add a folder on your Mac for copying files, select Folders and add it as appropriate, it will then appear in Windows File Explorer on your Cloud PC. macOS can also use multiple monitors via the Remote Desktop client, if you want to see that in action click here. iOS (iPad/iPhone) With iOS you have two options of connecting, namely a web browser session and the Remote Desktop client. Keep in mind that the web browser session lacks the same abilities as the Remote Desktop client. Installing the Remote Desktop client For more features use the Remote Desktop client which is available in the App Store. If you browse to https://windows365.microsoft.com and login using the credentials of a Cloud PC user that has a Cloud PC provisioned, you'll see that Microsoft Remote Desktop for iOS is highlighted, and it links to the App Store. clicking on that link opens the App Store. Click Get and install the app. you'll get a few prompts, answer them as appropriate. and Adding a workspace After the app is installed, you'll need to add a workspace. To do that, go back to the web browser session and copy the subscription URL. In the Remote Desktop client, click on Add workspace and paste in the copied subscription URL. Click Next and enter your credentials when prompted. The Cloud PC will be listed in your Workspaces. Accessing remote desktop features After launching the Cloud PC from the Remote Desktop client, you'll notice a toolbar at the top of the screen (screenshot from iPad). There's a magnifier icon to zoom in on sections (useful on a small screen) and a keyboard icon to get a virtual keyboard. Clicking the Remote Desktop icon in the center brings up some additional options. It's useful to note that the touch icon gives you easy control of the mouse pointer, but if you have a Bluetooth mouse connected to your iPad you can use the mouse icon. We tested a Teams video meeting from the iPad Cloud PC and it worked, and streamed video via the iPad camera as you can see here. You can always verify what settings are enabled for the Remote Desktop client in the iPad/iPhone settings. Android (tablet/phone) We also tested connecting to Cloud PCs from Android phones and an Android tablet. You can again access your Cloud PCs via a web browser or via a Remote Desktop client. You'll need a recent release of Android OS however to run the Remote Desktop client. Installing the Remote Desktop client To download the Remote Desktop client, you can get it directly from the Windows 365 web page shown below by clicking on the link or download it from Google Play Store. After installing the Remote Desktop client, you'll be prompted to allow audio etc. Adding a workspace Once again, as with other supported operating systems, you have to subscribe to a workspace URL in order for this to work as simply downloading the app is not sufficient. Copy the URL by clicking on Get subscription URL in the web page. Click on the + symbol, then select Add workspace, Paste in the subscription URL copied from the windows365 web page. Approve the MFA request, and the Cloud PC will appear in the client. Accessing remote desktop features It became obvious quite quickly that Android did not support video (camera) for Teams meetings (or anything else), even with the Remote Desktop client. keep that in mind if you intend to support Android devices for Windows 365. Apart from that missing feature, it acted quite like the iOS equivalent with a toolbar at the top of the screen and worked well in our tests. Linux Niall has taken a look at accessing Windows 365 Cloud PC's using a web browser in various Linux distros here. Linux based Windows 365 support is via a web browser connection, meaning that you are limited to what that provides (no video meetings for example). Related reading Redirection options with Remote Desktop - Remote Desktop - compare the client apps redirections | Microsoft Learn Multi-monitor support - https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/windowsdesktop Multi-media redirection - https://learn.microsoft.com/en-us/azure/virtual-desktop/multimedia-redirection?tabs=edge Using multiple monitors with Windows 365 - https://www.windows-noob.com/forums/topic/23081-how-can-i-use-multiple-monitors-with-windows-365/ Configure DNS Feed Lookup for RemoteApp and Desktop Connections - https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831442(v=ws.11)#configure-dns-feed-lookup-for-remoteapp-and-desktop-connections Summary Using a Windows 365 Cloud PC gives you the power to get your work done anywhere via the operating system of your choice. We did note some short comings such as the lack of a Remote desktop client from Microsoft for the Linux OS and the lack of video support in the Remote Desktop client for Android. Web based sessions can only do so much and the lack of these features on Linux/Android will leave you with the inability to host video meetings in Teams, Webex or Zoom, so keep that in mind if it's important to you.

what exactly are you trying to accomplish ? you can use shutdown events in event viewer to trigger a scheduled task to run a powershell script, that would probably be better, but even so, when a computer starts shutting down, it shuts down services etc that you might need, so again, what are you trying to solve here ?

Introduction Cloud PCs can come in certain preset configurations based on templates, or you can choose to customize your own. Sometimes you may find that a Cloud PC is not powerful enough for a user, or is too powerful and not being used to it's full potential (low utilization). With the Windows 365 Cloud PC resize (preview) remote action you can resize low utilization (or high utilization) PCs on the fly to get the most out of your investment. Identifying low utilization You can now identify low utilization on Windows 365 Cloud PCs in the Intune portal directly. In the Devices overview click on the Cloud PC performance (preview) tab highlighted here. This will reveal Cloud PCs with connection quality issues or Cloud PCs with low utilization. clicking on View report under Cloud PCs with low utilization reveals more data. You can see the Total time connected and even the Days since last sign-in which easily gives you an idea of how often your Cloud PCs are used and when they were last used. Clicking on any of the devices will reveal even more data. Below is the overview of one of our low utilization devices. Notice the Performance (preview) option. clicking on Performance (preview) reveals data about it's utilization. And you can dig deeper by clicking on any of the three highlighted reports. for example, in the Time connect to device report, we can see how long a user was actively connected to the Cloud PC over a given period (7 days/28 days) You can use this data to help decide which Cloud PCs are low utilization and based on that resize them to a more cost efficient model. Resizing Cloud PC requirements You'll need one of the following (or custom equivalent) roles: Global Admin Intune Service Admin Intune Reader + Cloud PC Admin roles The Cloud PC must have a status of Provisioned in the Windows 365 provisioning node The Resize remote action supports the following licenses paid preview trial Note: Resizing isn’t supported for Cloud PCs provisioned through group-based licenses. Resizing is only supported for Gen 2 Cloud PCs. I've asked Microsoft PG to explain how we can determine the Generation (Gen 1 versus Gen 2) of a Cloud PC and will update this blog post when they reply. The Resize remote action Now that you've identified a Cloud PC to resize you are ready to perform that action, but before you do it would be a good idea to communicate this to your end user as the resize action will logoff any logged on user. Not only will it logoff the user but that action will not send any notification to the end user on the Cloud PC itself, nothing will popup on the device it will just shutdown. Depending on how the user is connected to the device they might even see the following shortly after the device has shutdown. In the Intune Portal, select the Cloud PC you intend to resize and you'll see the Resize (preview) option. Clicking Resize (preview) brings up available resize options, note that you can resize up or down (the resize down was added based on customer feedback, so yes Microsoft does listen to feedback). Note: You can submit feedback for anything Windows 365 related via https://aka.ms/w365feedback. I have one license available for 4 vCPU, 16GB ram so I'll select that (it's actually an upgrade, but let's give it a test). Here is the current spec of my Cloud PC (8GB ram, 2vCPU). The specs of your existing Cloud PC that you intend to Resize are listed in your Resize options also under the Current size heading. Select a resize option that is available to you and then click Resize. Note that if you click a SKU upgrade that isn't available then you'll get a red warning informing you of that. You'll be prompted to confirm the resize operation, and have to click Resize for a third time. In the Intune portal you'll get a notification that the remote action was started Back in the Intune portal, the resize option is now greyed out for the selected Cloud PC and the status has changed to Resize pending. You can probably refresh this view in Intune for a few minutes/hours, but I got impatient and attempted to RDP back to the device. To my surprise it was already resized, however the RDP session was not yet aware of that. Side note: That disk sure looks busy after the resize ? It did calm down shortly after, but it's probably worth keeping in mind that directly after a resize things might need a few minutes to stabilize. At this point, I went back to Intune and refreshed, and now it updated the remote Resize (preview) action to Completed. However, it still listed the old specs under Device Model. This may change after a hardware inventory is sent back to Intune but I did trigger a SYNC and it's still wrong. Update: After checking the same device the following morning in Intune, it correctly reports the Device Model. If you look at Provisioned PC's, the data there is correct and it shows the new size under PC Type. Licenses As part of the resize the affected user is moved from their current Cloud PC license, to a valid license for the target model. In the resize done previously where we resized a Cloud PC from 2vCPU 8GB Ram to 4vCPU 16GB Ram, the license involved would move from one Cloud PC type to the other, below is a screenshot of the licenses before the resize. Notice how there is one 'free' license available in the Windows 365 Enterprise 4 vCPU, 16 GB, 128 GB. and below is what those same licenses look after the resize is complete. Actually, the license move happens right at the beginning of the operation and if there are no licenses available the resize operation will fail in the Intune portal. I have got to admit the Resize remote action was impressive, and very fast, but I'd like to see some improvements however such as: Custom email notification (to user/group/admin about the resize about to occur) Customizable ALERT toast notification sent to the user warning them to save their data Custom alert/email sent to user/admin notifying them that the resize is completed or if there was an issue, describe it that was it for this blog post, see you in the next one If you'd like to get started with Windows 365, checkout our brand new series here. cheers niall

Introduction I use PKI based labs to test various scenarios from Microsoft. I've multiple SCCM (Configuration Manager) labs that are running in HTTPS only mode (PKI) using a two tier PKI infratstructure (Offline Root CA, Issuing CA). Using multiple labs usually means only one lab is online at a time, and as certs expire regularly, an offline lab can mean expired certs. You'll first notice issues if you do OSD regularly as it depends on a healthy PKI infrastructure. If you have expired certs, PXE boot will not work. In this video I show that problem, reveal the expired certificates on the IssuingCA and show you how I fix it. Setting up PKI I've created multiple guides to help you setup PKI in your LAB and to integrate it with SCCM. You can review them below. Part 1 - Introduction and server setup Part 2 - Install and do initial configuration on the Standalone Offline Root CA Part 3 - Prepare the HTTP Web server for CDP and AIA Publication Part 4 - Post configuration on the Standalone Offline Root CA Part 5 - Installing the Enterprise Issuing CA Part 6 - Perform post installation tasks on the Issuing CA Part 7 - Install and configure the OCSP Responder role service Part 8 - Configure AutoEnroll and Verify PKI health How can I configure System Center Configuration Manager in HTTPS mode (PKI) - Part 1 How can I configure System Center Configuration Manager in HTTPS mode (PKI) - Part 2

please see my reply above yours