Month: June 2020

If you are MCT (Microsoft Certified Trainer) and can not access to the Learning Download Center (https://learningdownloadcenter.microsoft.com/) and see the error: Access Denied Microsoft Certified Trainers should login with Microsoft Certification Account. Microsoft Partners should login with their active Microsoft Partner Account. For more information on Microsoft Partner Account click here. For further support please contact Microsoft Support. You have to: Visit the MicrosoftCertification Dashboard Migrate Page (https://mcp.microsoft.com/MCP/Home/Migrate) using Internet Explorer (recommended browser). Sign in with your preferred Microsoft account and password that you would like to link with your Microsoft Certification profile Enter the Access Code along with the MC ID to have your Microsoft account associated with your Microsoft Certification record. The access code you must acquire by creating New Discussion on Microsoft Trainer Forum (https://trainingsupport.microsoft.com/en-us/tcmct/forum). It is the only way to get support with this and you receive it via Private Message – Yes there is functionality with private messages – look at the topic you will create there will be the sign Private Message.

Jeżeli nie możesz uwierzytelnić się w Recovery Services vault upewnij się, że czas na serwerze jest prawidłowo ustawiony. Agent generuje TOKEN SAS, który jest ważny godzinę na podstawie zegara w AZURE i jeżeli na serwerze rozjazd czasu będzie ponad godzinę nie uda się uwierzytelnić. Zazwyczaj towarzyszy temu błąd: Invalid vault credentials provided. The file is either corrupted or does not have the latest credentials associated with recovery service. (ID: 34513) We recommend you download a new vault credentials file from the portal and use it within 2 days. Logi przechowywane są w C:Program FilesMicrosoft Azure Recovery Service Agenttemp I prawdopodobnie w pliku CBEngineCurr.errlog znajdziecie coś podobnego do: Client assertion is not within its valid time range. Current time: 2020-06-27T17:23:32.8614131Z, expiry time of assertion 2020-06-27T16:34:05.0000000Z. Jeżeli backup System State zakończy się błędem: Error in backup of C:windowssystemroot during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect. Należy poprawić wpisy sterowników wykorzystywanych przez mechanizm VSS – wg dokumentu: https://support.microsoft.com/en-us/help/4053355/microsoft-azure-recovery-services-agent-system-state-backup-failure należy to zrobić dla wszystkich sterowników, w których znajdziemy w rejestrze poprzedzające „/”.   If you cannot authenticate with Recovery Services vault, make sure the server time is set correctly. The agent generates SAS TOKENS, which is a … Microsoft Azure Recovery Services (MARS) agent – z dziennika wdrożeniowca / from the Azure Administrator JurnalRead more

If someone comes to putting VM on VM (Nested Virtualization – already possible in Azure on Dv3 machines), it will probably be useful using NAT – how to run Win2016 and Win10 Step by Step: New-VMSwitch –SwitchName “NAT” –SwitchType Internal New-NetIPAddress –IPAddress 172.16.0.1 -PrefixLength 24 -InterfaceAlias “vEthernet (NAT)” New-NetNat –Name NATnetwork –InternalIPInterfaceAddressPrefix 172.16.0.0/24   You can also use it in your laptop.   Z dziennika wdrożeniowca – jak komuś przyjdzie stawiać VM na VM (Nested Virtualisation – już możliwe na maszynach Dv3 w Azure) zapewne przyda mu się NAT – jak uruchomić w Win2016 i Win10 Step by Step: New-VMSwitch –SwitchName “NAT” –SwitchType Internal New-NetIPAddress –IPAddress 172.16.0.1 -PrefixLength 24 -InterfaceAlias “vEthernet (NAT)” New-NetNat –Name NATnetwork –InternalIPInterfaceAddressPrefix 172.16.0.0/24   Powyższe można oczywiście używać na laptopie.  

Sometime during scaling operation on Azure Kubernetes Services, it hangs on  Provisioning State: Scaling. Manually deleting VMs from the MC* group may have had some impact as well on this operation. Solution: Upgrade the AKS cluster to the same Kubernetes version it is currently in (in this case, 1.13.5) from Azure CLI or CloudShell. Step by step: az aks upgrade –resource-group myResourceGroup –name myAKSCluster –kubernetes-version 1.13.10 Check status: az aks show –resource-group myResourceGroup –name myAKSCluster –output table More information here.