ITGURU

I have 1000 or so users I am migrating from local exchange to office 365. I have about 10 users that have a 365 mailbox and local mailbox, but the local exchange one is used, not 365. For migrated users sending emails to accounts which have both local and 365 accounts the emails are going to the 365 mailbox and not local Does anyone know if using the PermanentlyClearPreviousMailboxInfo for the cloud account will mean the user will also lose all teams chats? Theres nothing mail wise in the cloud mailbox which matters, but I believe teams chats are stored in the mailbox, however if a user currently doesnt have a 365 mailbox where would the chats be stored? Thanks.

The only update I cannot get is firmware for the tape drive as dont have active warranty/support on it, but wouldnt have thought would be the issue? Only proof i've got is to downgrade back to 2016 and re-test but not the way moving forward.

Its All HP Hardware and the tape drive is connected to an independent SAS card.

I have a server which has an LTO 6 tape drive which backs up the local server it is attached to - 1.2TB of data. When the server was on server 2016 the backup took around 8-10 hours to complete and transfer speeds around 2000-3000 MB/Minute. I did a clean install on the c drive of server 2019, reinstalled the Backup software (CA Arcserve), and all the HP drivers, however when i run the job the local disk backup to take is now transferring at between 500-800 MB/Minute. No hardware has changed, only difference is operating system from 2016 to 2019. backup job is the same source etc. Not sure what to look for that could be the issue. Any help would be grateful. Tapes pass HP Tools tests, HP drivers are installed, tried both Media driver and official HP driver with no change. Power settings set to high performance. thanks.

Followed this and all is well again even after adding a 3rd dc everything now populates everything as expected - Force synchronization for Distributed File System Replication (DFSR) replicated sysvol replication - Windows Server | Microsoft Docs

Looking for some help following a discovered issue. After doing a disaster recovery, I brought online a bare metal backup of the PDC hosting all roles. 2 other DCs were offline and from AD deleted the objects which clears up the meta data leaving the single DC online of which works fine users can login and all sysvol etc shares are there. I then spun up another VM, joined to domain, replicated and rebooted, Ad works fine, can connect to either server. However, the second / replicated DCs have none of the sysvol, netlogon shares etc. Please could I ask for some help how to get the second DC's back replicating properly from the PDC. Thanks.

Apologies if this has been asked before but what is everyone using to backup their 365 tenants and how do you find it? Have you ever had to restore mailboxes etc and how easy has it been. Looking at potential costs , Thanks

AH OK. If users search powershell in the start menu, they cannot open the folder, but if powershell_ise shows in the start menu as a search result, it still loads

That imported the 2 allowed rules, but not any of the deny ones, the code has non formatted characters presumable from the way its being pasted in.

I have saved the code as xml and tried to import but get the error below

I have a GPO which prevents users loading powershell.exe however in the same policy i've added powershell_ise.exe but it only blocks the powershell.exe and not the ISE. Please could someone advise how to block the ISE properly so students are unable to access? Thanks

The odd thing is, I have the servers added to mremote aswell and when i select the server in that rdp software it connects immediately when using the FQDN so seems to be an issue with the RDP (mstsc) client.

I get the certificate warning even when using the IP address - but it just says the certificate is not from a trusted certifying authority which is as expected. whether i connect via IP address or DNS name I still get the certificate warning, just with the IP, the warning is instant, but using FQDN it stays on securing network connection for ages before the security warning pops up.

Go for a switch stack for your core. offers greater flexibility and redundancy if one switch dies rather than a chassis. currently have a 10gb ring between 4 switches, 2 coppers and 2 sfp switches so if lose one switch still have full redundancy with 2 x fibre links to edge (one from each switch) and servers 2 and 2 in the copper switches. All managed from Single IP interface.

Wondered if anyone can shed some light. It's always been when accessing systems by IP address it is instant and immediately goes past securing network connection and get the certificate issue, say yes to continue and immediately get the desktop. However if i enter the hostname or FQDN of the server in the mstsc box, it takes forever to get past the 'securing network connection' part- it hangs there for a long time before get the certificate warning to continue. What causes this when have no dns issues?

I will check. Which should be the default? when select another domain should it be prompting for authentication or now when clicking check name?

We are at MAT with two way forest trusts enabled between all the domains. For one domain, when we set security settings on a folder share, and we select the domain from the 'location' button which lists all the trusted domain, some of them I can select the domain enter username, click check and it will find the name, or popup with suggestions. However, for one of the domains, when i click 'check name' it pops up and wants to authenticate to the domain before it shows me the available matching users. Anyone know why this would occur for just one of the trusted 2 day forest domains?

It is still worth getting electricians in to explain the situation? Is it something they need to rectify or nothing wrong with these alerts etc? We have fixed wire testing every 5 years but guess they don't pick up on things like this?

This is the same UPS on another part of the site. completely different readings.

3 phase Substation on the school's site! all underground

here's the monitoring

I have several APC UPSs on site. During the normal week/working day I get no alerts of the UPS compensating for high input voltage. However, evenings and weekends I get several alerts. Other than turning off the email alert for this particular alert - is there anything else I need to look at which is causing this?

Why are we fixing something youtube changed, with a registry edit. Surely its for Youtube to fix?

I was going to put 2022 on our latest server as a Hyper-V host but saw the network configuration had changed since 2016/2019 so reverted back to 2019 for now until tested on spare server. Got about 3 member servers on 2022 been running for a few months. No issues so far, even on HP ML350 Gen 5 servers!

All updates have a black cross against then - when try to download it says all software udpates in this selection have expired or meta-data only, and cannot be downloaded