i put myself in a big problem
-
i didn't contacted the technical support, otherwise the issue will spread out
fortunately i was able to solve it by your advises -
@IT-ADMIN said:
i didn't contacted the technical support, otherwise the issue will spread out
fortunately i was able to solve it by your advisesThat's great. I'm glad that it worked out so well.
The power of MangoLassi!!
-
@Dashrender said:
You had an entire day of downtime on this and no one noticed?
only the one who was working on the payroll software was having a connection error, i told him that we have a problem in the server, so he stop working on it until this morning when things come back to life
fortunately the issue occur at about 6 PM and we finish the shift at 7 PM therefor the employee didn't complain because he was about to finish his shift -
there is a big time diffidence btw qatar and US, when i post my problem it was early morning in US but it was the end of the day in Qatar
-
@scottalanmiller said:
@IT-ADMIN said:
i didn't contacted the technical support, otherwise the issue will spread out
fortunately i was able to solve it by your advisesThat's great. I'm glad that it worked out so well.
The power of MangoLassi!!
yeah, off course you are great guys
-
@IT-ADMIN said:
@Dashrender said:
You had an entire day of downtime on this and no one noticed?
only the one who was working on the payroll software was having a connection error, i told him that we have a problem in the server, so he stop working on it until this morning when things come back to life
fortunately the issue occur at about 6 PM and we finish the shift at 7 PM therefor the employee didn't complain because he was about to finish his shiftPeople who know me know I'm a gambler. I go to Vegas all the time, I blow money at various casinos throughout the country.
You just rolled a quick point on the craps table, you hit a blackjack on your first hand, you laid down $5USD on 21 red and it came up. You got seriously lucky. By pure chance you got out without anyone being the wiser.
One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.
Remember, the worst thing you can do as a gambler is go and do things without thinking. When I sit down and play blackjack, I have a good idea about the cards, the odds, where we are in the deck, what is available, what is not available. I calculate the risks, rewards, and make my decisions on that. As one should do when working on anyone else's machines.
-
@PSX_Defector said:
@IT-ADMIN said:
@Dashrender said:
You had an entire day of downtime on this and no one noticed?
only the one who was working on the payroll software was having a connection error, i told him that we have a problem in the server, so he stop working on it until this morning when things come back to life
fortunately the issue occur at about 6 PM and we finish the shift at 7 PM therefor the employee didn't complain because he was about to finish his shiftPeople who know me know I'm a gambler. I go to Vegas all the time, I blow money at various casinos throughout the country.
You just rolled a quick point on the craps table, you hit a blackjack on your first hand, you laid down $5USD on 21 red and it came up. You got seriously lucky. By pure chance you got out without anyone being the wiser.
One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.
Remember, the worst thing you can do as a gambler is go and do things without thinking. When I sit down and play blackjack, I have a good idea about the cards, the odds, where we are in the deck, what is available, what is not available. I calculate the risks, rewards, and make my decisions on that. As one should do when working on anyone else's machines.
yeah it was a good lesson for me, next time before doing any major change like this i will post it in ML to discuss with you the consequences, once it is approved then i will be ready to go
for the approval of the management (because Scott emphasize on this) they don't understand what active directory mean or what an additional domain controller mean, they are really far away from IT, so they told me do what should be done as long as it is free hhhhhh
for this reason i'm playing around with the servers and enjoy my time because no one understand what i'm doing (they understand only one thing : is the system down or not) so basically they know 0 or 1, -
@PSX_Defector said:
One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.
One more thing that has to be considered - the reward. How big is the payoff? In this scenario, the payoff, had everything worked perfectly, was effectively zero. There was risk without potential reward. That's a big deal too. He would not really have benefited here, even if things had not gone poorly.
-
@scottalanmiller said:
@PSX_Defector said:
One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.
One more thing that has to be considered - the reward. How big is the payoff? In this scenario, the payoff, had everything worked perfectly, was effectively zero. There was risk without potential reward. That's a big deal too. He would not really have benefited here, even if things had not gone poorly.
Agreed. This is betting on every horse in the race. Yeah, you win, but what do you get out of it? Maybe a dollar or two assuming that the longshot came in. If it was the 2-1, you are out money on the process.
See the road ahead, understand what is next, what you next move is, and it will usually work out. Something some folks don't understand.
-
in my case i put my self at risk without any reward, because even my goal was not achieved (additional DC)
the only reward i get is a lesson : before doing anything in your system you have to study the consequences -
you know guys, i thinking of promoting the server application again hhhhhhhhh
i know some of you will insult me looooool
what do you think guys -
@IT-ADMIN said:
you know guys, i thinking of promoting the server application again hhhhhhhhh
i know some of you will insult me looooool
what do you think guysNo, do not do that. Having a DC on that box was not important before and doesn't follow best practices very well. Yes, having two DCs is best practice, but so is having the DC on its own VM, having virtualization on every server, taking snapshots, taking backups. If you are considering going to install the DC again you are not learning your lessons from this thread already. You know that having a second DC has little reward for you, so why take on risk?
-
@IT-ADMIN said:
you know guys, i thinking of promoting the server application again hhhhhhhhh
i know some of you will insult me looooool
what do you think guys
-
If you are looking for projects to do, look for ones that fix problems rather than create them. Don't implement change or take on risk just for the sake of doing it, focus on things that will fix the environment. Until you have backups and have virtualized, don't even think about putting in a second DC. You have the cart before the horse.
-
@PSX_Defector said:
@IT-ADMIN said:
you know guys, i thinking of promoting the server application again hhhhhhhhh
i know some of you will insult me looooool
what do you think guyshhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
you are funny dude -
Do you have a means of virtualizing in place? Or better yet, let's start by talking about your backups.
-
ok ok ok
i'm just joking guys
you are awesome -
@scottalanmiller said:
Do you have a means of virtualizing in place? Or better yet, let's start by talking about your backups.
actually i was trying xenserver and virtualize 2 VM : freepbx and pfsense and everything was ok, but this project was not very important, it is only for a garage, kind of a home lab
for the production environment we have 2 dell poweredge T310 :- DC & file server (16 GB RAM and has 4 HD with software RAID 1)
- application server (8 GB RAM and has 2 HD with no RAID)
so i'm really afraide to touch anything especially how to P2V
-
P2V is very safe. It does not destroy the "P" while making the "V", it just makes a copy. So you can do it for testing very safely.
-
@IT-ADMIN said:
- application server (8 GB RAM and has 2 HD with no RAID)
So no RAID, no backups, no snapshots, no virtualization.... this is crazy.
