@irj said in When people ask you what you do...:
al quick....?
Sure, I charge $50 an hour.
That's the only way to make it stop.
@irj said in When people ask you what you do...:
al quick....?
Sure, I charge $50 an hour.
That's the only way to make it stop.
"Her team found that coffee was associated with fewer deaths due to heart disease, cancer, respiratory disease, stroke, diabetes and kidney disease".
Sounds exactly like snake oil...
https://vimeo.com/trishapasricha/about
An internal medicine resident that wrote the article.
Dr. Trisha Pasricha, MD at Johns Hopkins Hospital.
I screwed up and need help!
We have two locations, each have its own domain controller and they are in the same forest. Site A DC just host DC's stuff, DHCP, DNS, and etc. Site B's DC is also a file server, print server, as well as all the dc server's stuff. We have an in house exchange 2010 server at Site A. All three servers are virtual ESXi guest running Server 2008R2, and we also have other servers join to the domains, but they are application servers.
This morning, I noticed the exchange server have only 5% of free space left, I tried to free up some space by deleting old administrators users inbox, but exchange will not let me saying I don't have the permission to do so. Following https://community.spiceworks.com/topic/386021-cannot-delete-ad-user-insufficent-rights-or-protected-from-accidental-deletion
"Tommy6473 Jan 14, 2014 at 4:11 PM 1ST POST
I had the same issue where "Protect object from accidental deletion" was NOT checked, and I still couldn't delete.
Here was the fix I found: In AD Users and Computers, Go to the object's properties > security tab > click Advanced > click "Restore Defaults".
Close out the windows, then try deleting again."
It says to go to the AD, then the object, then security page and reset the security to default, then delete the users. I somehow went the AD security for the object's folder and change the security to "default". Suddenly, 90% of the exchange email inbox were gone from the exchange server.
After tracing my steps to figure out what happened, I restored DC1 to yesterday 7pm backup, then left it off. Use DC2 for DNS so users have at least have internet. I'm in the process of restoring Exchange to the yesterday's 7pm backup now, which will take several more hours before it finish.
My plan is to bring up DC1, then bring up Exchange, make sure they are good to go and have no issue, then I will probably have to rejoin all users computers and applications server to the domain.
Questions I have are,
Does my plan of action sounds alright? We only have 35 users, so rejoin domain won't be too bad.
What do I do with DC2?
How would DC2 react to this restore DC1?
How do I prevent the AD security settings on DC2 to go to DC1? Would they even sync?
How do I keep the file share settings on DC2?
Any things I am missing?
Any and all advise are welcome.
Thank you
I made a conscious decision to stop drinking soda: with diet, syrup, or sugar. Coffee smells great to me, taste awful, so I never got started. Once in a while I'll have a cup of tea, but I can go a week without tea and no headaches or other withdrawal symptoms.
A hot shower makes me up in the morning.
Would it be a better idea to make DC2 seize the FSMO roles, then copy the security settings from the offline DC1 to DC2, then bring up the Exchange. Once Exchange is verify working, create another server and join it to the domain then promote it to DC. Then use DC2 to do a Force demote on a the offline DC1?
I had three locations with three DCs, all are VM guest, and all are server 2008 R2.Site A, DC1. Primary DC, runs DNS, DHCP, and whatever else DC runs.Site B, DC2. Secondary DC, runs DNS, DHCP, File Server, and Printer Server for site B, three employees.Site C, DC3. I'm not sure what it runs, there is no employee working there, so I have not spend any time to look into this.Due to the incident on Tuesday, https://community.spiceworks.com/topic/1993055-need-advise-restoring-domain-controller-and-email-ser... , I am left with an
orphaned DC1 that I have kept offline, but I still have access to it and can view DHCP configurations. I made DC2 seize all 5 roles of FSMO, and it is running DNS. DHCP is currently not working on DC2, event 1046 about not authorized to start. The DHCP scope is not setup. I can see the scope on DC1. I didn't touch DC3 at all.
Questions, do I just want to fix the DCHP on DC2 or just build a new DC and run DHCP from there instead?
I plan to:Build a DC0 using DC1's old IP addressAdd DC0 to domain and make it a DC, setup DNS and DCHP scopes
Once DC0 is running good, then delete DC1 from the AD.
Do I have this right? I'm sure I'm missing a few steps. Thanks for your comment.
I want to go back to cash only.
So, I backed up the DHCP on DC1, save it on the virtual drive, then add that virtual drive on DC2, authorized DC2 to be the DHCP server and then restored the DCHP. DCHP is working again!
Will work on DC0 and DC1 tomorrow.
The user is a GOLD mine for answers!!!
Ask the user more open ended questions.
"When is it crashing?"
"What's the computer doing when it crash?"
"How is it crashing?"
"What do you do to resolve it?"
"How often does it crash?"
"Can you cause the crash intentionally?"
etc
@guyinpv said in Synology one bad sector crashes whole volume RAID0:
Interestingly, I force turned off the Synology, pulled the drives and did a quick canned air cleanup.
Turned back on and it came to life. Looking at the drive screen, the count of bad sectors is now at 38.
This makes no sense, jumping from 0 bad to 38 out of the blue.I know enough about drives to know they can recover from bad sectors and avoid those areas of the disk. It's weird to me that it would bring down the entire volume and crash the whole thing over a bad sector.
It's gonna fail again. No it's not, it's RAID 0, it needs EVERY sector. Think of it as a password, lost one character, you lost the entire password.
@guyinpv said in Synology one bad sector crashes whole volume RAID0:
The NAS has 2 x 4TB WD Red drives. I'm running them striped since I wanted more space and perhaps speed.
...
SATA drives speed > 1 Gbps, there was no speed advantage. Since you didn't need the space, all you did was add risk by running RAID 0.
Maybe for you, I get
An error occurred while processing your request.
Reference #30.1f35d417.1539958032.10cfa6db
OS on RAID 1 and DATA on RAID 5 is so out dated.
Think about it, why would you want HyperV OS to be fast, but data to be slow? You reboot once every 6 months, so you want that boot up to be super fast, but the data you use every second you want it super slow?
If you have to choose, you'd want the data to be fast, NOT slow.
A company is wanted 3 years of footage of NVR and I calculated they needed about 1.5PB of storage.
I see Dell EMC has a Isilon Scale-Out NAS Storage line that looks nice.
What devices do you use?