How to display video on Barco wall in VLC from NGS device

First note the IP of NGS device of which you want to display the video on Barco wall.

Type the IP and access in web browser as below.

https://192.168.12.12

select settings tab and then select Encoder settings and go down to "HDMI in" and there is steam 0 and stream 1, select the concern stream and right click on rtsp and select copy link.

Now open the VLC tool on the barco wall. From Media menu select Open network steam and past that copied URL. i.e it will be like "unsafe;rtsp://192.168.12.12/HDMIIn/v2dstream0" 

Delete the unsafe; from the above URL and hit enter.

Now the video should be displayed in the VLC in barco wall. 

How to install SCCM client manually on windows machine

To install SCCM agent on client windows machine, first download the source file to the windows machine on which you want to install the agent. place it in a folder, go to that path in command prompt and run the following command. 

ccmsetup.exe /mp:sccm.abc.com SMSSITECODE=101 SMSMP=sccm.abc.com FSP=sccm.abc.com DNSSUFFIX=abc.com

ccmsetup.exe /mp:NameOfManagementPoint SMSSITECODE=101 SMSMP=NameOfManagementPoint FSP=FallbackStatusPoint DNSSUFFIX=DomainName

For further detail, please visit Client installation parameters and properties - Configuration Manager | Microsoft Learn

Disable the First things First popup in office 2013

To disable the following message in office 2013. You may do the following registry changes.

[Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Registration]
“AcceptAllEulas”=dword:00000001

 

To disable the following message in office 2013. You may do the following registry changes.

[Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\General]
“OptInDisable”=dword:00000001

How to change Microsoft Exchange services startup type to automatic and start the services

 Issue:

There are some security patches of Microsoft exchange server which change the startup type of exchange services to disable from automatic, Due to which these services would not auto start after deploying the patches.  changing the startup type of these services may be time consuming and the better option would be to use the following command in exchange PowerShell. 

Get-Service | Where-Object { $_.DisplayName -like "Microsoft Exchange *" } | Set-Service -StartupType Automatic

Get-Service | Where-Object { $_.DisplayName -eq "IIS Admin Service" } | Set-Service -StartupType Automatic

Get-Service | Where-Object { $_.DisplayName -eq "Microsoft Filtering Management Service" } | Set-Service -StartupType Automatic

Get-Service | Where-Object { $_.DisplayName -eq "World Wide Web Publishing Service" } | Set-Service -StartupType Automatic

Get-Service | Where-Object { $_.DisplayName -like "Microsoft Exchange *" } | Start-Service

Get-Service | Where-Object { $_.DisplayName –eq “IIS Admin Service” } | Start-Service

Resolved: This computer is a member of a database availability group (DAG). It must be removed from the DAG before you can uninstall Exchange.

Issue detail:

Was trying to decommission Exchange 2019, but was getting the following error.

 "Error:

This computer is a member of a database availability group (DAG). It must be removed from the DAG before you can uninstall Exchange."

Resolution:

From role and feature, remove the failover cluster feature and reboot the system and then try again to start the uninstall from control panel/uninstall program.

the above error was no more.  

The message was rejected by a rule set at the organization level.

 The message was rejected by a rule set at the organization level. 

Which Transport Rule Was Applied to an Email Message (practical365.com)

Resolved: An unknown error has occurred in outlook. mail could not be sent. the message has been moved to your drafts folder.

Issue: an unknown error has occurred in outlook. mail could not be sent. the message has been moved to your drafts folder. 

Issue detail:

User A has full access on user B mailbox. have migrate User B mailbox to Exchange 2019 recently, but User A was still on Exchange 2013. After that the issue was started (User A was unable to send email from User B mailbox, of which he has the rights)

Before migration of user B mailbox, there was no issue, User A was able to send the emails from User B.

Solution:

Did two things to resolve this issue:

1. migration User A as well to exchange 2019
2. Assign the permission again on User B to user A.