Just remember that the main lugs are always live in a breaker box. And make sure you get the right amperage breaker and the right gauge wire for the amps. It's pretty easy after that. Just slot the breaker in, wire in the run and flip the switch.
Assuming I'm no electrician, the main lugs are probably the pieces from the that are before the main breaker directly from the meter/service?
This is using the power of deductive reasoning like I'm some kind of Sherlock Holmes.
The hot bus bars should be de-powered if the main breaker is flipped though right?
better than conductive reasoning
+3
lwt1973King of ThievesSyndicationRegistered Userregular
User: It says on the email it's from "[email protected]" so it must've come from them.
"He's sulking in his tent like Achilles! It's the Iliad?...from Homer?! READ A BOOK!!" -Handy
Worst case I'm figuring I'll pay my electrician friend to come over and do the whole thing.
Fixed it for you.
Seriously, from what you've written, you know just enough to get yourself in trouble.
Just call up your friend, pay him, and let him wire it for you.
If he's a good friend, he'll give you a good rate.
Well you'd like to think physically running the wire is something bowen could handle. Most of us have run a shitload of wire in our lives. Just let the electrician terminate it.
Because like, how can you even retain that much data? If I had to retain everything we'd be looking at data center sizes of data.
Jesus. I would not want to deal with retention on email at all, ever.
SAN storage, son. Also, you have Exchange (or a third party app) archive messages over a certain date and prune your mailbox databases. The archives go to long term storage.
Heh, my company just gave everyone 1 GB of inbox and disallowed PST's. Everything auto-expires after 90 days as well (unless you specifically mark it to keep)
That is going to cause some anger in about 3 months.
Oh, we've been doing it for a year or so. There are pieces to it I think are BS (as someone who gets a lot of data files that I need to tie to people), but I imagine at a corporate level it works great.
That would cause some massive legal issues here. Retention periods are a thing.
That's why we're doing it. We have retention groups, but the general gist is that you retain according to the official schedule, otherwise 90 days. We also have pretty robust integrations around legal holds and discovery-related stuff, so that covers that side of things as well.
Do you guys get sued much? Cause 90 days doesn't usually even cover the time before declaration of litigation, much less the full potential time frame of an issue. The company I worked at before got sued a lot. Like, 5-15 times a month. If we were just straight dumping messages over 90 days, our lawyers would have shit a Buick.
Ahahahahahahaa, yes, all the time. We're a fortune 100. It's actually been largely driven by the lawyers, as if we're dumping based on published policies, it's ok. That said, we have a number of other document management systems for the items we typically would get sued for, so those are being retained separately from people's random interdepartmental emails about cake or meeting invites.
The main goal was to eliminate the pack-rats who kept every email in perpetuity for internal projects that had no bearing on anything we may be sued over. We have a whole host of backup solutions and ediscovery stuff on the important things.
Worst case I'm figuring I'll pay my electrician friend to come over and do the whole thing.
Fixed it for you.
Seriously, from what you've written, you know just enough to get yourself in trouble.
Just call up your friend, pay him, and let him wire it for you.
If he's a good friend, he'll give you a good rate.
How do you figure? It's pretty much the easiest of all the electrical runs.
Double pole breaker, 220v, 10/3 romex, run from point A to point B, flip main to Off, carefully wire both ends, rubber mat, don't touch exposed wire as they may be live.
Done, panel back together, power that shit back on, call it a day, eat a pizza.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
But yeah if I can't do the terminations, I'd pay him to do at least that. No point in wasting a half hour of his time to pull a wire through a wall and along a crawlspace.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
But yeah if I can't do the terminations, I'd pay him to do at least that. No point in wasting a half hour of his time to pull a wire through a wall and along a crawlspace.
You should still run your whole plan by your electrician pal, and let him fill you in on the details, because you're sure to miss details that only an electrician, up to date on the current housing codes for your area, would know. And I'd still let him do the terminations, because he's got the tools to shut down the electricity to your whole house, before the breaker box.
Well, the spammers are getting smarter. The more your email address gets out there, the wider the flood gates open up. I keep trying to explain this to the users, but they think I'm (a) lying to them, (b) trying to get out of doing my job, (c) lazy, or (d) all of the above.
While I agree that being insensitive is an issue, so is being oversensitive.
Anyone have a good idea on how to restrict all accounts that have local admin rights from installing anything, requiring domain admin credentials to do so? I'm looking into software restriction policies on the local machine, but it seems way more restrictive than I want; I also have zero experience with this type of policy setting.
Why do users have local admin access? Normally, they do not. However, we just installed a Mondopad and (after painfully picking through some of the settings) have found a way to enable networked drives to show up in the Mondopad shell*. Unfortunately, only users with local admin access have them displayed on the shell. Otherwise, they have to minimize the shell to get to the OS desktop. That being the case, we have to give all users local admin access if we want them to access the networked drives via the shell; we're pretty much trying to force users to use the Mondopad shell instead of "It's new, I don't want to use it" mentality.
*The shell is an overlay on top of the desktop. Without networked drives displayed in the shell, users have to either (1) email the file to a designated address, which puts the file in a folder on the local drive of the Mondopad, (2) browse to the Mondopad's internal web server, enter an access code, then upload the file, which puts the file in a folder on the local drive of the Mondopad, or (3) locally copy the file from the originating folder to the folder on the local drive which allows the file to be displayed and used in the Mondopad shell.
While I agree that being insensitive is an issue, so is being oversensitive.
However I've found a strong PC/network useage policy to be very good at discouraging shit. That means that HR and your bosses all have to stick by their guns.
First time is a warning, second time is an immediate can. If you go a year without incident, you can get another warning.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
None of those 3 solutions you outlined seem bad goat. If your business users are balking, tell them to suck it up. None of those actions are onerous on the users, as it probably takes less time to do it that way than to navigate to it in the shell.
Are your users actually logging into the mondopad as themselves?
Personally, I'd just give the mondopad a generic user account, then tell the users "Sorry, the mondopad has to use this special account, it doesn't have access to your network shares. If you want to use a file please copy it to [location where mondopad has access]"
EDIT: Hell make C:\mondopad\library a shared folder, give domain users r/w access. Then they can add stuff from their own devices. If someone bitches about their stuff going missing give them a libray\user folder that only they can write to.
Aioua on
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
Users are logging into the Mondopad as themselves due to file permissions on the network. We don't want someone from one department accessing the files from another department and so forth: sales getting into HR, HR getting into sales, etc. Those departmental folders are located in a single mapped drive (let's say F:) and then permissions dictate who can view/access what (e.g., F:\HR, F:\Sales, F:\IT). If I created a generic logon account, I'd have to choose between restricting all access to the F: drive or granting all access (which isn't going to happen).
That being said, we're trying to accommodate the actual needs while catering towards some wants. Unfortunately, "catering towards some wants" has over the last couple of years turned into pampering and changing diapers; it pisses me off, but I have no say in the matter. It's gotten so much worse and I don't see that trend stopping; it's 100% asinine.
I've considered the idea of sharing the Mondopad library directory and mapping the drive for easy access, but (referencing the notion above) it would be viewed by the users as "inconvenient" and I'll be told to find a better way, which leads back to this same problem. However, I think this notion might be the best alternative.
While I agree that being insensitive is an issue, so is being oversensitive.
Could you just make a symbolic link inside the mondopad directory to the F:\whatever folder?
Edit: Also, does it actually need the permissions to access the folder, or does it just want them? Could you fool it into thinking it was running as admin with the compatibility toolkit?
Could you just make a symbolic link inside the mondopad directory to the F:\whatever folder?
Edit:Also, does it actually need the permissions to access the folder, or does it just want them? Could you fool it into thinking it was running as admin with the compatibility toolkit?
That, I do not know. I've tried putting a shortcut to the F: drive within the folder, but the shell doesn't like it. We haven't quite figured out what it is that's causing it aside from the obvious local admin rights thing.
This is still very new to us, so we're trying to tweak it and already done a ton of that already. Some of it just doesn't seem intuitive at all. There is a chance I'm making this more difficult than it needs to be.
While I agree that being insensitive is an issue, so is being oversensitive.
Could you just make a symbolic link inside the mondopad directory to the F:\whatever folder?
Edit:Also, does it actually need the permissions to access the folder, or does it just want them? Could you fool it into thinking it was running as admin with the compatibility toolkit?
That, I do not know. I've tried putting a shortcut to the F: drive within the folder, but the shell doesn't like it. We haven't quite figured out what it is that's causing it aside from the obvious local admin rights thing.
This is still very new to us, so we're trying to tweak it and already done a ton of that already. Some of it just doesn't seem intuitive at all. There is a chance I'm making this more difficult than it needs to be.
I know it's probably futile, but have you opened up a ticket with the manufacturer asking them why the hell it needs admin rights in the first place?
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
I've already called them a couple of times and fully plan on calling again to figure that out. The answer really depends on who answers the call, because the first person didn't answer much while the second support guy was pretty good with helping, although he did say that there was no way to have mapped drives show up in the shell and we found a way to... hmmmm
I'm sure this will be an awesome product once we work out all the kinks. It better be, at least, because unit 2 is being installed next week.
Le_Goat on
While I agree that being insensitive is an issue, so is being oversensitive.
Could you just make a symbolic link inside the mondopad directory to the F:\whatever folder?
Edit:Also, does it actually need the permissions to access the folder, or does it just want them? Could you fool it into thinking it was running as admin with the compatibility toolkit?
That, I do not know. I've tried putting a shortcut to the F: drive within the folder, but the shell doesn't like it. We haven't quite figured out what it is that's causing it aside from the obvious local admin rights thing.
This is still very new to us, so we're trying to tweak it and already done a ton of that already. Some of it just doesn't seem intuitive at all. There is a chance I'm making this more difficult than it needs to be.
A shortcut or an actual symbolic link? If it's a symlink the program shouldn't be able to tell the difference, unless of course there is something actually preventing access.
Wow, my head is not in it today. While trying to clean up an issue in Patch Manager, I accidentally deleted an entire group from WSUS, which also removed all approved updates from that group... whoops! Thank god for working backups, though.
While I agree that being insensitive is an issue, so is being oversensitive.
First off, the symbolic link worked like a charm in fooling the shell into displaying it in the GUI. Unfortunately, if a non-local-admin user clicks the link within the GUI, the shell crashes. For some reason, network access within the GUI requires administrative privileges. Off to a nice chat with their tech support again. Regardless, thank you @LD50 for the suggestion; I'm ashamed that I've never used symbolic links until now.
While I agree that being insensitive is an issue, so is being oversensitive.
Why is a glorified network card for my APC 2200 (which is the only way to manage more than one server) almost $250?
It's a network card, not a goddamn unicorn horn.
I wondered the same thing when we bought 4, but in a way it can be a unicorn horn if your UPS shits the bed at 3:30 am and the NIC alerts the servers to gracefully shut down. I'm pretty sure that's what they are banking on.
While I agree that being insensitive is an issue, so is being oversensitive.
Why is a glorified network card for my APC 2200 (which is the only way to manage more than one server) almost $250?
It's a network card, not a goddamn unicorn horn.
I wondered the same thing when we bought 4, but in a way it can be a unicorn horn if your UPS shits the bed at 3:30 am and the NIC alerts the servers to gracefully shut down. I'm pretty sure that's what they are banking on.
Did you end up running a switch through the same UPS to make sure it had power so the network card could do its job?
Why is a glorified network card for my APC 2200 (which is the only way to manage more than one server) almost $250?
It's a network card, not a goddamn unicorn horn.
I wondered the same thing when we bought 4, but in a way it can be a unicorn horn if your UPS shits the bed at 3:30 am and the NIC alerts the servers to gracefully shut down. I'm pretty sure that's what they are banking on.
Did you end up running a switch through the same UPS to make sure it had power so the network card could do its job?
The switches that everything is plugged in to all run through UPS units, so yeah. However, the way that the application works is that if the server loses communication with the UPS unit (for whatever time you specify), the application will begin to gracefully shut down the server, with the assumption that if communication was lost, maybe the UPS flat out died. That being the case, I don't think it would really matter if you did or didn't.
Le_Goat on
While I agree that being insensitive is an issue, so is being oversensitive.
Posts
better than conductive reasoning
Seriously, from what you've written, you know just enough to get yourself in trouble.
Just call up your friend, pay him, and let him wire it for you.
If he's a good friend, he'll give you a good rate.
Ahahahahahahaa, yes, all the time. We're a fortune 100. It's actually been largely driven by the lawyers, as if we're dumping based on published policies, it's ok. That said, we have a number of other document management systems for the items we typically would get sued for, so those are being retained separately from people's random interdepartmental emails about cake or meeting invites.
The main goal was to eliminate the pack-rats who kept every email in perpetuity for internal projects that had no bearing on anything we may be sued over. We have a whole host of backup solutions and ediscovery stuff on the important things.
220 will fuck you up. My friend almost got killed from badly labeled breakers with weird circuit runs in an old house.
How do you figure? It's pretty much the easiest of all the electrical runs.
Double pole breaker, 220v, 10/3 romex, run from point A to point B, flip main to Off, carefully wire both ends, rubber mat, don't touch exposed wire as they may be live.
Done, panel back together, power that shit back on, call it a day, eat a pizza.
It was a multi-year project, we just have some very motivated people in compliance and a good CIO.
To shut it off at the meter I'd have to pay our electric company like $100.
Mmmhmmm, and what's your co-pay for trips to the ER?
Bowen's guide to accidental death insurance fraud, on sale now!
Those are driving me mental. We keep getting the one that says the attachment is an important e-fax. Sails right through our spam filters.
Why do users have local admin access? Normally, they do not. However, we just installed a Mondopad and (after painfully picking through some of the settings) have found a way to enable networked drives to show up in the Mondopad shell*. Unfortunately, only users with local admin access have them displayed on the shell. Otherwise, they have to minimize the shell to get to the OS desktop. That being the case, we have to give all users local admin access if we want them to access the networked drives via the shell; we're pretty much trying to force users to use the Mondopad shell instead of "It's new, I don't want to use it" mentality.
*The shell is an overlay on top of the desktop. Without networked drives displayed in the shell, users have to either (1) email the file to a designated address, which puts the file in a folder on the local drive of the Mondopad, (2) browse to the Mondopad's internal web server, enter an access code, then upload the file, which puts the file in a folder on the local drive of the Mondopad, or (3) locally copy the file from the originating folder to the folder on the local drive which allows the file to be displayed and used in the Mondopad shell.
However I've found a strong PC/network useage policy to be very good at discouraging shit. That means that HR and your bosses all have to stick by their guns.
First time is a warning, second time is an immediate can. If you go a year without incident, you can get another warning.
Personally, I'd just give the mondopad a generic user account, then tell the users "Sorry, the mondopad has to use this special account, it doesn't have access to your network shares. If you want to use a file please copy it to [location where mondopad has access]"
EDIT: Hell make C:\mondopad\library a shared folder, give domain users r/w access. Then they can add stuff from their own devices. If someone bitches about their stuff going missing give them a libray\user folder that only they can write to.
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
That being said, we're trying to accommodate the actual needs while catering towards some wants. Unfortunately, "catering towards some wants" has over the last couple of years turned into pampering and changing diapers; it pisses me off, but I have no say in the matter. It's gotten so much worse and I don't see that trend stopping; it's 100% asinine.
I've considered the idea of sharing the Mondopad library directory and mapping the drive for easy access, but (referencing the notion above) it would be viewed by the users as "inconvenient" and I'll be told to find a better way, which leads back to this same problem. However, I think this notion might be the best alternative.
Edit: Also, does it actually need the permissions to access the folder, or does it just want them? Could you fool it into thinking it was running as admin with the compatibility toolkit?
This is still very new to us, so we're trying to tweak it and already done a ton of that already. Some of it just doesn't seem intuitive at all. There is a chance I'm making this more difficult than it needs to be.
I know it's probably futile, but have you opened up a ticket with the manufacturer asking them why the hell it needs admin rights in the first place?
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
I'm sure this will be an awesome product once we work out all the kinks. It better be, at least, because unit 2 is being installed next week.
A shortcut or an actual symbolic link? If it's a symlink the program shouldn't be able to tell the difference, unless of course there is something actually preventing access.
\d makes it a directory link. Make sure not to use /j, junction points don't work for stuff not stored on the local system.
Edit: actually, you might want to try \j if \d doesn't work, it won't do anything bad if it fails, and it might work since the drive is mapped.
It's a network card, not a goddamn unicorn horn.
Did you end up running a switch through the same UPS to make sure it had power so the network card could do its job?