Wednesday, February 21, 2024

W365: Error code 0x80072ee2

Recently i started seeing the below error message when accessing cloud pc through the windows app. 

The connection cannot proceed because the authentication authority cannot be contacted.

Error code: 0x80072ee2


Steps taken to resolve was quite simple. 

Try closing down windows app forcefully. 

Even if it fails to connect to windows 365 cloud pc next time then restart the base laptop which should fix this error. 


Wednesday, February 14, 2024

w365: How to Enable Local admin settings

 Steps to Enable Local admin settings:

  • Log in to the Microsoft Intune portal.
  • Navigate to Devices -> Windows 365 
  • Click on +Add button to create user settings policy.

  • Select the Enable local admin checkbox ☑ 

Now assign it to the group of users who require local admin access. 

In the cloud pc, open company portal and in settings click sync.

Logoff/Login required for the settings to take effect.

Wednesday, January 10, 2024

w365: Embracing the Future: Switching to Windows 365 and Its Benefits

In the ever-evolving landscape of modern work environments, businesses seek innovative solutions that offer flexibility, security, and efficiency. Windows 365 emerges as a game-changer, revolutionizing how organizations operate by providing a seamless, cloud-based PC experience. This blog explores what Windows 365 is, why it’s beneficial, and how switching to this platform can transform your business.


 What is Windows 365?


Windows 365 is Microsoft’s cloud-based service that streams a full Windows experience from the Microsoft Cloud to any device. It essentially transforms your physical device into a high-performance cloud PC. With Windows 365, users can access their personalized Windows environment, including apps, data, and settings, from anywhere and on any device with an internet connection. Windows 365 is managed through Intune whereas Azure virtual desktop is managed through Azure portal. 


Key Benefits of Switching to Windows 365


1. Enhanced Flexibility and Accessibility


One of the primary advantages of Windows 365 is the ability to access your desktop from anywhere. Whether you're working from home, a coffee shop, or traveling, you can log into your cloud PC and pick up right where you left off. This flexibility is crucial in today’s hybrid work environments, where employees are no longer confined to a single physical location.


2. Seamless User Experience


Windows 365 offers a consistent and personalized user experience. Your desktop, apps, and settings are always available and up-to-date, regardless of the device you're using. This eliminates the frustration of configuring settings or installing software repeatedly on different devices.


3. Improved Security


Security is a paramount concern for businesses of all sizes. Windows 365 leverages Microsoft’s robust security framework, providing enterprise-grade protection. Data is stored and processed in the cloud, reducing the risk of data loss or theft from physical devices. Additionally, features like multifactor authentication, secure boot, and Microsoft Defender for Endpoint ensure comprehensive security.


4. Simplified Management and Maintenance


Managing and maintaining physical hardware can be complex and time-consuming. Windows 365 simplifies this by centralizing the management of cloud PCs. IT administrators can easily deploy, update, and manage cloud PCs through the Microsoft Endpoint Manager, reducing the overhead associated with traditional device management.


5. Scalability and Cost Efficiency


Windows 365 offers scalable solutions that can adapt to the changing needs of your business. You can quickly scale up or down based on your workforce requirements without the need for significant capital investment in hardware. This scalability is particularly beneficial for businesses with fluctuating staffing needs or those experiencing rapid growth.


6. Enhanced Collaboration and Productivity


With Windows 365, collaboration becomes seamless. Employees can share and access files in real-time, using familiar tools like Microsoft Teams and OneDrive. This fosters a collaborative work environment, enhancing productivity and ensuring that teams stay connected and efficient, regardless of their physical location.


How to Transition to Windows 365

 Assess Your Needs


Before making the switch, assess your organization’s needs. Consider factors such as the number of users, required computing power, and specific business applications.

Plan and Prepare


Develop a transition plan that outlines the steps for migrating to Windows 365. Ensure you have the necessary infrastructure, including reliable internet connectivity and compatible devices.

 Train Your Team


Provide training sessions to help your team understand how to use Windows 365 effectively. This will ensure a smooth transition and help employees leverage the platform’s full potential.

Implement and Monitor


Deploy Windows 365 across your organization and monitor its performance. Gather feedback from users and make any necessary adjustments to optimize the experience.

Conclusion


Switching to Windows 365 represents a strategic move towards a more flexible, secure, and efficient work environment. By embracing this innovative platform, businesses can unlock new levels of productivity, collaboration, and scalability. As the future of work continues to evolve, Windows 365 stands out as a vital tool for organizations aiming to stay ahead in a dynamic and competitive landscape.


Explore the possibilities with Windows 365 and take the first step towards transforming your business into a modern, cloud-powered powerhouse.

Wednesday, October 18, 2023

Solution: TortoiseSVN Background contextmenu not visible after publishing

After publishing the App-V sequenced TortoiseSVN, all the context menu shortcuts are visible and it works fine. Only the background context menu option is not visible. In this blog, I will demonstrate and provide a solution for it.


First download the TortoiseSVN software from the below link.
https://tortoisesvn.net/downloads.html


Download the Latest windows ADK so that we can use the latest App-V Sequencer from the below link.
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install


Sequence the TortoiseSVN application using default steps.


Even if you use PVAD when sequencing, we can see the same issue that the background context menu is not visible after publishing.
After Publishing the sequenced package, we can see that when we right click file\folder\drive the context menu option is visible as App-V will install those respective registry entries in the local machine and they will be used by the explorer due to dynamic virtualization concept.


FILE:





FOLDER:



But when we right click on empty explorer window or inside any folder empty place, the below options are not visible as seen in the native installed package.






We can see that in the sequencer machine, the following registry responsible for the background context menu is registered in the local machine.









Even in the package editor we can see that those registry keys are captured.





Even in the AppxManifest file we can see those shell entries.







But after publishing and seeing the local HKCR registry, the particular key alone is missing. All other context menu registries are visible.










Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers\TortoiseSVN]
@="{30351349-7B7D-4FCC-81B4-1E394CA267EB}"


To Fix the issue, copy the above registry key and install in native machine.To Add it with the sequenced package, first export the AppxManifest.xml file and edit it using AVME from the below link.


Edit the XML file and add like below in AddPackage and Remove Package tabs.



Once done save the AppxManifest.xml file and import it back to the package using sequencer.




Save the package and publish it to the client machine. Now you can see the context menu when you click on empty explorer window or empty space inside directory.
You can also add the registry using scripts in deploymentconfig/userconfig file too.

As pointed by Roy Essers in a TechNet post, this indeed seems to be App-V sequencer bug and MS needs to fix this soon.