ozydave

Morning, I'm not great with Mac's so any help would be great. Students log on with their AD credentials and have their windows document shares mapped and a mapping to my papercut print server. Disabling SMBv1 on my windows serves now breaks the mapping of the shares. We are using workgroup manager on the Mac server. I have applied the Microsoft patch to plug SMBv1 but as MS say I need to disable it. Any offers on how I can get round the mapping issue? Cheers

That surely has to be a new kinda virus - possibly called the "Bloody Hell" strain

Here's the next version to worry about Uiwix https://heimdalsecurity.com/blog/security-alert-uiwix-ransomware/

Yep, If you done have FSRM installed on server in question run the script reboot then run again it will then created the file screen templates. I already had FSRM on one server so just ran the script. It knew I had it installed but just created the screen templates

Just been applying the script for FSRM to my servers. It just works Cheers

I have to say, bloody good news this is!

I wouldn't worry to much about MS classroom! Microsoft Classroom is ending! /showthread.php?t=183852

No outage just the phishing Glad you wasn't hit by it [emoji106]

Sumg as long as your gmail wasn't effected today [emoji3][emoji3] Just glad we use 365 mail [emoji106][emoji106][emoji106][emoji106]

As others have said the Noob guides are great. From memory the only real pain was getting all the install prerequisites.

SCCM here

Hmmm. Deleted and restored again from a different backup. Same problem. I ran VMware converter and converted the live server DC1 to the same VM host I used before, same isolated network and resource pool. Once I powered it on all was well. I could start active directory users and computers, dns, group policy etc. I done the same with DC3. So DC1 and DC3 were happily replicating AD and DNS objects. It must be something that happens during the Veeam restore process, or the settings I’m choosing ( I’m pretty much choosing the defaults)! I do use Veeam’s Surebackup on the DC’s every other day so I am sure the backups are good. Thanks for the replies

Ditto That!

Cheers, I'll move the roles tomorrow, run backups and restore to test again.

started DC1 and DC2. I can start the DNS management on both servers (both have DNS role). I can ping each DC form the other by ip and domain name. I added a static DNS entry to DC2. this is not replicating to the DC1

The IP addresses are the same in the live environment as they are on the recovered test DC. The restored DC1 and DC2 in the isolated network can ping each other by ip address. didn't think to check till just now if they can ping each other via server name Will let you know

just run dcdiag. Amongst the output is the primary domain controller could not be contacted.

Cheers, I use Veeam for backups. I've restored the DCs to a separate host on an isolated network. I've restored DC1 and DC2 and they can ping each other. Yep all 5 FSMO roles are held by DC1. DC2 and DC3 both confirm DC1 has the roles when running netdom query fsmo in the live environment. just going to run the dcdiag in the test enviro. Will post back in a tick

Cheers Yep DNS is on this DC1. The network card points to itself. I have also restored DC2 to the test environment. Still Domain cannot be contacted. DC2 also points to istself

I have 3 DC’s all Virtual servers DC1, DC and DC3. Everything appears to be running fine apart from the odd group policy not applying to laptops. DCDIAG /test:DNS on all 3 DCs are good. Objects created on any DC replicate to the others, DNS records also replicate. DC1 has all the FSMO roles Netdom query fsmo confirms this. This is also confirmed by DC1 and DC2 with Netdom query fsmo. So now my problem…. I have restored DC1 to a test network to test the recovery. No problems with the recovery and DC1 started, I was able to login with the domain admin. First thing I done was run Netdnom query fsmo which reported there was no domain. Active directory user and computers will not start Domains and trusts will not start Group policy management will not start All saying they cannot contact the domain So if this domain controller is supposed to hold all the FSMO roles surly active directory users and computers would start. If the FSMO roles are on DC1 that is where the domain is This would suggest to me all is not well in my live environment. Am I just being a plank?

I would loved to be able to swear on this forum. Pearson just makes my blood boil. They should not be let anywhere need software

Thanks for my pay rise

My internal domain Certificate authority has gone bang. I can’t get it back (that’s another story) Currently my domain laptops connect via wireless authenticating against NPS. As the certificate pushed out to the clients is still valid the laptops are still connecting. I cant get the CA back. My domain still thinks the CA is there but just can’t contact it. Read a few posts on the net where a similar thing has happened and they have just setup a new server with the old server name joined it to the domain and installed the CA role. Anyone think this is the way to go? Or just setup a new CA, get it issuing certificates for NPS, but how do I remove the failed CA from the domin? Cheers

990 pupils and 125 staff

We are 7mil sheets of paper since September 2013 SLT don't want to do much about it!