Thursday, December 30, 2021

Office can't be activated because it doesn't meet the requirements for running on remote

 Error :

When user tries to open office applications and gets the error,

 

Office can't be activated because it doesn't meet the requirements for running on remote

 

in Terminal/RDS server the following error may occur:

This copy of Microsoft Office 2016 cannot be used on a computer running Terminal Services. To use Office 2016 on a computer running Terminal Services, you must use a Volume License of Office.

 

Troubleshoot:

Please confirm whether the office product installed as Office 365 ProPlus on a remote desktop server through ODT deployment.

 

Fix/Solution:

If it is not installed by ODT then try to install using ODT installation method.

 

If yes,

Open the registry editor (Win+R > regedit) and go to this path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration

Add the SharedComputerLicensing (Reg_SZ) key and set its value to 1.

(or)

Press Win+R and run gpedit.msc to open the local group policy editor.

Edit the policy or create this policy if it doesn’t exist:

Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Licensing Settings

Enable the 'Use shared computer activation'.

Monday, December 13, 2021

Error: bad allocation Failed to upload disk in Veeam backup

 


Issue:

When I try to backup Hyper-V environment got the below error, 

Error: bad allocation Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Reconnectable protocol device was closed. Unable to retrieve next block transmission command. Number of already processed blocks: [825]. Failed to download disk 'FIleName.vhdx'.  


Cause:

Bad Allocation - This issue due to high usage of either CPU or memory.


Fix:

Checked the Hyper-V and found that the VM is using too many resources (both CPU and memory), try to reduce the resource usage or reboot the server to make server normal usage.

---

Once server became normal backup started work normally.




Monday, December 6, 2021

Unable to create azure subscriptions : check the user has administrative privilages on the specific Azure account

Issue: 

I'm trying to restore whole VM in from Hyper-V backup job in to MS Azure. When I add account in to Veeam server getting below error,


"Unable to create azure subscriptions : check the user has administrative privilages on the specific Azure account "

We are not sure why Veeam is trying to create a new subscription while adding credential. Could you check and help us to check this case.

We found only below log in our log files

[19.10.2021 14:40:46] Info Connecting to Azure by Power Shell
[19.10.2021 14:40:46] Info Login to Azure Account
[19.10.2021 14:40:46] Info [PS] 'Add-AzureRmAccount'. Arguments: EnvironmentName='AzureCloud'.
[19.10.2021 14:41:04] Info [PS] 'Get-AzureRmContext'. Arguments: .
[19.10.2021 14:41:04] Info [PS] 'Get-AzureRmADApplication'. Arguments: IdentifierUri='https://VeeamAzureApp';ErrorAction='SilentlyContinue'.
[19.10.2021 14:41:05] Info [PS] 'Get-Module'. Arguments: n/a.
[19.10.2021 14:41:07] Info Registering application in AD
[19.10.2021 14:41:07] Info [PS] 'New-AzureRmADApplication'.
[19.10.2021 14:41:07] Info Disposing splash form
[19.10.2021 14:41:07] Error [Veeam Backup and Replication] Unable to add Azure subscriptions: check that user has administrative priviliges on the specified Azure account

my Finding:

I have tried to add account under the version 10.0.1.4854 and got this error, however after I upgraded to veeam 11 it works fine.

Note : I believe this is Veeam version issue and raised the issue to Veeam Team but they refused it. Someone has same issues on Veeam 10 and fixed it?

Email sent from a shared mailbox are not saved to the Sent Items

  Issue : When a user sends an Email from his delegated (shared) mailbox the Email which sent from the delegated mailbox are stored in user...