The unit was an Elitedesk 800 G3
Download the driver bundle from here : http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html
Extract the Drivers then Import them into Out of Box Drivers on your MDT Share
Once done Update Deployment Share
Once done , replace image on the Microsoft Deployment Services
WIM’s will be installed to
C:\DeploymentShare\Boot
Had a ticket regarding 3 different sent emails to 3 different third parties which were getting duplicated into an IT mailbox on Office 365.
I double checked the “rules” under Mail flow to make sure there were no BCC rules for the users sending which there were not.
In MailTrace the emails came up as Status “Expanded”. This means the email has been sent to a group, however the original email was sent to a Single External Email address?
Why was the external email being displayed as a group in 365?
Turns Out the Outbound Spam Preferences had been turned on! And for whatever reason, these items were triggering the BCC of suspicious messages!
Recently trying to release and whitelist an item using Barracuda’s cloud Spam filter. however was getting the below error:
The message couldn’t be downloaded either. Tried from Multiple pcs and still an issue
Trying the next day and the issue was fine which shows it must have been something on Barracuda’s side!
If you navigate to your Calendar Tab in Outlook App
Click on this icon
Then Add Shared Calendars
Changes to the Distributed File System (DFS) namespace are made on the domain controller with the PDC Emulator role. DFS root servers periodically request updated metadata from it. Inaccessibility of the PDC Emulator may result in incorrect operation of the DFS.
How to find you PDC
NetDOM /query FSMO
Recently during a DR test we spun up a file server that was protected using Microsoft Shared Cluster Services. The drives where mapped using a Physical Lun. Zerto protects this as long as you backup the Active Node of the cluster.
On Startup you need to change the VM Scsi mapping from Physical to None
Once booted , you should stop the Cluster Service and start is again with the /fixquorum flah
net start clussvc /fixquorum.
Now open the Cluster Manger and remove the Disks from the Server ( you will need to do this twice for each drive )
Once removed , stop the cluster service
bring Online the Disks in Computer manager.
If the disks come up as Raw , you will need to go back and perform a ReSync , then bring up again
Recently had a customer that was getting 15 – 20 minute delays in receiving emails from MailChimp. The same email to services such as Office 365 , Gmail and other email providers came through straight away.
We had whitelisted Mailchimps IP’s per below from Greylisting and Spam to no avail. The Message tracking proved that the message wasn’t hitting the Administration console for the 15 Minutes delay
Source IP Ranges (n.n.n.n/x):
205.201.128.0/20
198.2.128.0/18
148.105.0.0/16
We lodged a Mimecast support ticket and got this escalated to Level 2 and waited a week for a response. In the end a retry of the issue with the technician came through straight away which means there must have been a block somewhere in Mimecast
Recently after a reboot of a server, it came up as errored in our monitoring. I couldn’t ping it however when I logged into it, I could ping out ( Firewall! ). The network Profile for the Network card had changed from Domain to Private which automatically blocks ICMP and RDP.
The server might have started faster than the Domain Controller due to Windows Updates.
You can change the Profile Category of a Network Adapter per below
Set-NetConnectionProfile -NetworkCategory DomainAuthenticated
However
Set-NetConnectionProfile : Unable to set NetworkCategory to 'DomainAuthenticated'. This NetworkCategory type will be set automatically when authenticated to a domain network.
Restarting the Network Location Awareness service fixed this and change this backt to Domain
Recently we had jobs for a server showing up the error : NFC storage connection is unavailable
Turns out a colleague had added a server to the Veeam application with a tape drive to the unit which had actually added that server as a Veeam Backup Proxy!
Jobs actually default to “Use Any Available Proxy” so the Jobs were using the tape drive server as a proxy for some of the Jobs hence the NFC Failure
Recently we swapped a users UPN on a local domain controller ( which syncs to 365 via AAdconnect) to another domain and SMTP alias, all worked well however she could not login to Skype for Business.
Resetting Windows Credentials, Caches and registry items still would not fix this.
Most of the time this is due to the SIP Address not being correct. Little did we know this user had Lync before migrating to 365 so they had a SIP address in the attribute editor
Changing this resolved the issue