The Microsoft Azure Fundamentals certification (AZ-900) is an entry-level exam, introducing Azure to technical and non-technical people. The test covers a range of general cloud concepts and Microsoft products. This exam gives students a firm foundation to continue learning Microsoft Azure and to participate in the infrastructure shift from on-premises to the cloud.
This exam measures your ability to describe the following concepts: cloud concepts; core Azure services; core solutions and management tools on Azure; general security and network security features; identity, governance, privacy, and compliance features; and Azure cost management and Service Level Agreements.
the exam skills outline below .
Describe cloud concepts (20-25%)
Describe core Azure services (15-20%)
Describe core solutions and management tools on Azure (10-15%)
Describe general security and network security features (10-15%)
Describe identity, governance, privacy, and compliance features (20-25%)
Describe Azure cost management and Service Level Agreements (10-15%)
There are many great resources for the Azure Foundations exam.
https://www.simplilearn.com/ This course has a small fee but is an incredible resource and worth the price. They also have a monthly subscription if you wish to consume multiple courses in the Azure series
Microsoft intentionally created AZ-900 with a specific goal in mind: to provide the easiest transition possible to usher large numbers of people into using Azure professionally
The value you’ll receive is just as much from the journey and the experience as it is passing the actual exam. Once you pass the test, we recommend immediately starting to study for the exam that comes next in your chosen certification path. Building on knowledge and applying it within the Azure environment is critical to maintaining the momentum you just generated.
If you fall outside of these parameters and have prior cloud computing or Azure experience, skip AZ-900. There’s no dependency chain between this exam and higher-level exams or certifications, and it covers such basic material that virtually none of it is proprietary to any particular Azure certification. Your time is better spent studying for a higher-level exam that will lead to a Microsoft certification.
This error indicates that the virtual machine is not able to reach the App Volumes Manager because of an issue related to Appvolume manager
This error can have many reasons , during my deployments I faced multiple issued causing the same error message , to diagnostic this issue it require to check the App volume manager Server logs (check VMware KB https://kb.vmware.com/s/article/2114670 for additional use cases )
We are getting intermittent internal server error on the App Volumes Manager UI dashboard. In the logs we are also seeing SQL errors like “Invalid object name ‘settings'”
FATAL ActiveRecord::StatementInvalid (ODBC::Error: 42S02 (208) [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid object name ‘settings’.: EXEC sp_executesql N’SELECT [settings].* FROM [settings] WHERE (settings.type IS NULL OR settings.type IN (N”Rbac::RbacSetting”,N”Settings::Feature”,N”MachineManagerSetting”,N”Settings::AdvancedSetting”,N”Settings::BotConfiguration”)) AND [settings].[key] = @0 ORDER BY [settings].[id] ASC OFFSET 0 ROWS FETCH NEXT @1 ROWS ONLY’, N’@0 nvarchar(100), @1 int’, @0 = N’encryption_version’, @1 = 1):
Changed the ODBC connection to point directly to the App Volumes Manager database instead of the (Default) database.
2. it can occur if user configure port during Appvolume manager installation and Agent use different port (e.g. Manager use port 443 , agent use port 80)
To configure both App Volumes Manager and App Volumes Agent to use the same port:
Click Start > Run, typeregedit, and click OK. The registry editor opens.
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\svservice\Parameters.
Modify the entry for Manager1 to contain the port used by App Volumes Manager in place of the default port 80.
Note: The Port used by App Volumes Manager can be verified by opening your App Volumes Manager web interface.
Click Start > Run, type services.msc, and click OK. The Services window opens.
Restart App Volumes Service, and test again.
3. Another cause is if the address has been configure with IP instead of FQDN , if the certificate does not match , you will hit similar issues.
With VMware new Horizon 8 Horizon 2006 , VMware introduce new Optimization support for Microsoft Teams and zoom ,The Media Optimization for Microsoft Teams redirects audio calls, video calls, and viewing desktop shares for a seamless experience between the client system and the remote session without negatively affecting the virtual infrastructure and overloading the network. Teams media processing takes place on the client machine instead of in the virtual desktop.
The Media Optimization for Microsoft Teams offers the following features:
Accepting and making audio and video calls
Multiparty audio and video conferencing
Transfer, forward, mute, hold, and resume a call
PSTN calls via dial pad
Desktop screen sharing
Multi monitor screen sharing and screen picker for screen sharing
Volume control from the remote desktop
Active speaker identification
The Optimization for Microsoft Teams configuration Require :
Microsoft Azure /365 in backend : where the client would connect to establish the connection
Microsoft Teams Client (Optimized) x32 or x64 bit
Virtual desktop and client machine (where horizon client installed) operating system should be windows 10 x32 or x64 bit
Enough resource in virtual desktop : Minimum requirement is 2 vCPU
Network with IPv4, reachability of vDesktops and Horizon client to Microsoft 365
For Microsoft Teams offloading you need at least an advanced Horizon license
Limitation \ Not working:
Web browser horizon client is not supported
Still Linux and ThinOS do not support these feature
RDS hosts and application pools are not supported.
HID buttons to answer and end calls are not supported.
Virtual backgrounds are not supported.
Live events are not supported.
Desktop screen sharing give or take control is not supported.
Pop out chat is not supported.
Gallery View in meetings is not supported.
The camera light stays on if the user puts the video call on hold (but video will not be sent).
During a video call, when a remote desktop user starts a desktop share, the user’s video automatically turns off. After ending the desktop share, the remote desktop user can click the video button to turn the video back on.
Only one video stream from an incoming camera or screen share stream is supported. During an incoming screen share, that screen share is shown instead of the video of the dominant speaker.
To make it work it require to do configuration in 3 locations:
In vDesktops Master Image :
In End User Client/Thin Client
In AD Group Policy
In vDesktops Master Image :
Install Horizon Agent before you install Microsoft Teams (Horizon 2006 only , horizon 7.x is not supported )
The Media Optimization for Microsoft Teams group policy setting must be enabled to use the feature
Download the Teams MSI package that matches your VDI VM operating system using one of the following links: