So, its been a while, but lets start.
Today, I was googling how to deploy BGinfo Using SCCM. Everybody suggested on community to use GPO for this task.
I didn’t like that method because I like to have more info about deployment. Also we have AGPM Group policy in place and I hate all the authoring that comes with AGPM.
So the way I did it is that I created the config file, copy it on local disk and run script that kicks of the BGinfo.
Continue reading “Deploying BGInfo using SCCM”
Today, I had issue with one of the node cluster. After installing DPM agent on one of the nodes, the Server didn’t want to join to cluster. The error like this is not something to be happy about.
Cluster node ‘ServerName’ was removed from the active failover cluster membership.!
From cluster logs, I could see lot of event ID:1135
Continue reading “Failover Cluster – Node won’t join to cluster. EventID: 1135”
In this blog, we will cover moving protected server from one DPM to another.
In addition, we will refer to DPM from you want to move as Old DPM.
In addition, we will refere to DPM you want to move as New DPM.
Continue reading “Moving protected server from one DPM to another DPM.”
Issue and Logs
After checking through logs, I noticed that in 30 minutes interval we get bunch of Event ID 113 that source is MSiSCSI.
iSCSI discovery via SendTargets failed with error code 0xefff0024 to target portal *10.1.1.30 0003260 B06BDRV\L4SC&PCI_163A14E4&SUBSYS_045F1028&REV_20\5&6a108d3&0&30050200_0 .
Since, this host is part of Failover cluster, I was worried if we have some issues.
Based on Microsoft KB article it indicates the network issue.
Continue reading “iSCSI discovery via SendTargets failed – Event ID 113”
Event ID 1254 and 1069.
I came across with issue of unable to start VM. The affected resource was Virtual machine configuration file was “lost”
The event shows that Event ID 1254 and 1069.
Continue reading “Event ID 1025— Cluster failed to bring clustered role “VM1” online…”
Today, I came a cross with alert on my SCCM console regarding SUP synchronization.
After looking into WMC.log. The error log indicates that WSUS is unable to open and connect to DB. (internal DB)
Cannot open database “SUSDB” requested by the login. The login failed.~~Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’.~~
Continue reading “SCCM and WSUS (Cannot open Database “SUSDB”)”