kmount

Hanging on that means it's most likely storage connectivity. Check vmkping on each storage nic to each iscsi target ip and check if you're using jumbo frames or not.

Slow boot is common if the hosts cannot talk to DNS or storage. Check if they were configured to talk to DNS servers they host (so slower boot and timeout) - wouldn't explain sluggishness once those dns servers were up though. More commonly though is trouble accessing network storage like iscsi. I'd forget vcentre for now it's a victim too, look on the actual hosts for the storage pathing. If you're using iscsi and jumbo frames make sure they're still reaching with vmkping, and work your way up from there. Both hosts having the problem suggests something shared, switching or storage maybe. Log into the host client on each server and ssh/console and test the nics. Have a look in the vmkernel log too.

Hello, Welcome to Edugeek. Is this something your webfiltering solution could help with? Much in the same way you'd stop them going on inappropriate websites?

Have you allowed it through the RD Gateway CAP/RAP presuming you're using the gateway.

Yes, always use the vendor ISO (for drivers, etc) Going to 6.x won't cost you anything as long as service/support is paid up with VMware - if its not you probably want to figure that out. Being SDCard boot makes a lot of sense for ESXi, no need for raid controller, spinning disks etc. If there's really no vCenter then the VMs won't roam from host to host anyway, so you have no choice but downtime - but as there's a SAN one would hope there's a vCenter setup too to make this easier for you. I'd check your VMware support entitlement and plan to go up higher.

5.5 is end of life come September you want to be upgrading beyond that assuming your hardware is on the HCL. If you have vCenter (think of this like SCVMM in Hyper-V land) you can automate the updating centrally. But yes, the idea is you do vCenter first, then the hosts - you can boot from an ISO if you really want to but if you have vCenter+Update Manager in place you can upload the vendor ISO here and have it push it out + then the patches that follow. Drivers etc are all included in the vendor ISO assuming your servers are a relatively well known brand. Bit more info about the set up and we'll be able to steer you.

The Intel I350-T2 is probably on the mark for what you need - https://www.intel.com/content/www/us/en/ethernet-products/gigabit-server-adapters/ethernet-i350-server-adapter-brief.html

Hello, Check - https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=14587&vcl=true Reckons it's unsupported after 5.5u3. What server chassis are you using?

Fazza, I think you mean the community public in snmp you renamed - this isn't the same thing. It's the firewall zone and I suspect yours will still be public.

Condensing what you wrote to confirm - you cannot send from [email protected] (gmail) to [email protected] (exch) yeah? Do you get an NDR back into Gmail, and what does ECP say about the mail on Exchange side?

The VMFS datastore isn't something you can consume directly from windows client. (it doesn't do SMB natively) Spin up a VM and attach a disk to it from that datastore is the only way to do this I'm afraid.

Yep, or instead of having the full domain.co.uk zone internally consider using more specific ones like http://www.domain.co.uk and intranet.domain.co.uk so "unmatched" entries rely on your DNS forwarders (upstream DNS). (whereas what is happening now is unmatched entries return null because well, there's nothing there) If you have a long list of entries in your mydomain.co.uk zone you probably want to just go ahead and add the g.domain.co.uk mx record to match what you did for your public DNS.

Can you resolve the g.mydomain.co.uk from your internal DNS? (typically see this if someone has mydomain.co.uk as an internal DNS zone and forgets MX records)

I've seen hardware in the past (mostly really old Sun boxes) that won't power up from the ILOM(iDRAC) or the physical power button when the thing was actually broken and needed the motherboard replaced. The logs show up in the ILOM(iDRAC) as a simple "failure to power on". Gut says if it's not reached you a fit condition to turn it on it needs to go back or the supplier needs to provide support on at least the iDRAC password to get further into it.

Do you have memory dumps enabled to have a chance to analyse what is causing it to crash? (if not, enable them so they can be analysed to figure out what's happening) Event log saying anything useful?

Urgh, set locally.. If it's the only GP set you should find you can look through gpedit.msc locally to find the point and print stuff from the article.

Does it work as an administrator? There's lots online about the "start docPrinter" message. Anything interesting in the event logs after the message happens?

Hi, It does sound like point and print https://blogs.msdn.microsoft.com/7/2011/07/11/allowing-standard-users-to-install-network-printers-on-windows-7-without-prompting-for-administrative-credentials/

I wasn't particularly pleased with the quality of the bundled NVR setups. I ended up buying a few different onvif compatible cameras and playing with my own software setup. I started with Zoneminder (open source), and then after a problem with one of the cameras I'm now using Contacam (free, runs on windows) on a VM and it works really well. I use a few of these for outdoors - https://www.amazon.co.uk/gp/product/B073GQ8T2L/ and they work well in the dark which was important for me. Indoors (dog kennel) I use a pair of these - https://www.amazon.co.uk/gp/product/B018UN6K02/ mounted upside down. (quality now as good of course a 720p but they are fine for what I needed in their location)

Yup, was what I said - it will have lingered after a failed backup likely.

It is likely from a hotadd operation where your Veeam VM attaches other VM disks as read only to back them up. Check for snapshots etc.

Hi, What does the webserver error log file say?

Hi, I presume you only see these messages in the event logs on one of the two servers? (i.e. server B) Moving the SQL Server onto A is a good call, if the errors go away you know Server B does have a problem. I presume they don't share storage etc if you are replicating them in a pair so no reason to believe a common shared item is the culprit. See how it goes on A, if still slow - look for those errors to see if they have followed.

Hi, Nominet handle this. - https://s3-eu-west-1.amazonaws.com/nominet-prod/wp-content/uploads/2017/09/27104952/Schools_Domain_Name_Rules.pdf (lifted from https://www.nominet.uk/resources/policy/policies-rules/) EDIT: Beaten

Hi there, Try creating a primary zone for the specific url (not just the domain), all of the way down and this will work fine for you and avoid you needing to slave servers etc. i.e. add a primary zone for each: 10.0.0.1 - our.domain1.com 11.0.0.1 - customer.subdomain1.domain2.com 12.0.0.1 - customer.subdomain2.domain2.com This should work fine and allow you to avoid needing to put every record in for the domain.