|
Zero VGS posted:Let's say some other company's lawyers are theoretically asking us to hold documents for discovery. We all have Office 365 E3 Plan and I figured out how to search the criteria they ask for, and how to put a legal hold on that search. Here's some basic guidelines on document retention: http://resources.infosecinstitute.com/top-5-email-retention-policy-best-practices/ If I was king of IT, I'd rule that your mailbox is not an acceptable permanent storage location for anything that has a legal minimum retention time. It's the equivalent to keeping documents in piles on your desk, best case it's like having cardboard boxes full of hanging file folders stacked on your desk. I don't know the best way to do it, but for any emails that fit into categories that have minimum retention time, they need to be moved out of the primary email box and into a location that isn't affected by the retention policy.
|
#
?
Jun 2, 2015 23:52
|
|
|
|
| # ? Apr 24, 2024 18:25 |
|
|
Pass that request to your in house lawyers. Never try to gauge the expectation or demand of a request. They'll provide you the exact scope of the request and how to comply.
|
|
#
?
Jun 2, 2015 23:55
|
|
|
Zero VGS posted:Let's say some other company's lawyers are theoretically asking us to hold documents for discovery. We all have Office 365 E3 Plan and I figured out how to search the criteria they ask for, and how to put a legal hold on that search. I will answer you as I have performed the same duties regarding discovery. 1) They have a duty to clearly define what they are looking for, and your duty is to save the documents they ask for. It would be prudent that if you know they have made a minor mistake in their request (mispelled a name for example) you should ask for clarification from them. I wouldn't save anything they didn't ask for. I also wouldn't let them be intentionally vague, and if they were I would ask for guidance from my corporate counsel. 2) Your company should have a document retention policy and you should be following it. For example, if the policy says you won't save email for longer than two years, you should purge all email older than two years. If you don't have a policy defining your document retention periods, you should ask for direction from your management. Anecdotally, we archive all email immediately and retain it forever, but we purge email from exchange after two years.
|
|
#
?
Jun 2, 2015 23:59
|
|
|
Curious, with the storage a commodity why do companies have document retention at all? Why not simply save and archive everything? Yes, I know a commodity isn't free but for the sake of the argument.
|
|
#
?
Jun 3, 2015 00:05
|
|
|
Tab8715 posted:Curious, with the storage a commodity why do companies have document retention at all? Why not simply save and archive everything? Anything you save is a legal liability.
|
|
#
?
Jun 3, 2015 00:08
|
|
|
When I was at a previous company (I wasn't IT there) they were at constant threat of litigation and were told verbally never to commit certain things to writing. As I understood it, if you have no specific expectation of litigation, but you think people might in the future attempt frivolous lawsuits, then it might behoove you to set emails to expire at a quick pace, so that you're not constantly collecting evidence on yourselves. But, I.A.N.A.L. so for all I know that's not how it works at all. Dr. Arbitrary posted:Anything you save is a legal liability. Right, so I mean if it turns out we're not getting litigated, I should look into a short email retention time, and prevent archiving? For purposes of conserving local storage and bandwidth, of course.
|
|
#
?
Jun 3, 2015 00:12
|
|
|
Tab8715 posted:Curious, with the storage a commodity why do companies have document retention at all? Why not simply save and archive everything? 1) legal discovery 2) efficiency of searching and indexing (searching through 1 year of documents is easier than 10) 3) performance (which is tied to number 2) It is easy to fall into the digital packrat trap, and it's important not to unless you have a compelling reason to do so.
|
|
#
?
Jun 3, 2015 00:26
|
|
|
Zero VGS posted:Right, so I mean if it turns out we're not getting litigated, I should look into a short email retention time, and prevent archiving? For purposes of conserving local storage and bandwidth, of course. You should talk to a lawyer who knows what they're talking about, and find the legal minimum retention time. This is something you absolutely need backing from the CEO/President/Owner/God from. When people ask, tell them the new policy is to limit liability. Which is true. If it involves the threat of a lawsuit, get a lawyer. If it's something you don't know, get a lawyer. If it's something your in-house lawyer doesn't know, either you or they need to find someone who does. It may not be the case right now, but lawsuits can absolutely be end-of-the-world situations for companies. Do you want it to be YOUR fault when the company goes under? No? Talk to a lawyer. ETA: I want to say best-practice is no more than 7 years of retention. I am not a lawyer. This is not legal advice. Consult a lawyer.
|
|
#
?
Jun 3, 2015 00:29
|
|
|
Wizard of the Deep posted:ETA: I want to say best-practice is no more than 7 years of retention. I am not a lawyer. This is not legal advice. Consult a lawyer.
|
|
#
?
Jun 3, 2015 00:45
|
|
|
adorai posted:It is really going to depend on your business. Do you think a bank only retains the documentation (which includes communication via email) of a 30 year mortgage for 7 years? There is too much potential for loss if you do not retain every document possible for the life of the note. I don't think an exchange mailbox is an appropriate place for information on a 30 year mortgage either. Communications regarding that should be stored with the other relevant documents and probably expire 7 years after everything is wrapped up. So that means that the initial emails might get retained for 37 years, but they don't need to be sitting in random employee #82632's 'important mortgage email/2013/JohnDoe/ folder.
|
|
#
?
Jun 3, 2015 01:27
|
|
|
adorai posted:It is really going to depend on your business. Do you think a bank only retains the documentation (which includes communication via email) of a 30 year mortgage for 7 years? There is too much potential for loss if you do not retain every document possible for the life of the note. At my last place, we were obligated to keep the records of all manufactures for at least 20 years... after the death of the end customer. Medical manufacturing was one hell of a process.
|
|
#
?
Jun 3, 2015 02:40
|
|
|
adorai posted:It is really going to depend on your business. Do you think a bank only retains the documentation (which includes communication via email) of a 30 year mortgage for 7 years? There is too much potential for loss if you do not retain every document possible for the life of the note. Yup, the 7 years was only meant as a general/best-practices discussion. One place I worked several years back had to keep certain records for at least 60 years for certain civil projects, if it related to design or construction. If you're not sure, talk to a lawyer.
|
|
#
?
Jun 3, 2015 04:04
|
|
|
Tab8715 posted:Curious, with the storage a commodity why do companies have document retention at all? Why not simply save and archive everything? The only people to whom storage is a commodity are hyper scalers and reasonably sophisticated cloud shops. Everyone else still buys expensive arrays. The demand for storage is pretty rapacious as well so no matter how much you have you'll usually need more if you don't have sound data management policies. New applications aren't coming online every day so demand for compute and networking tends to be reasonably bounded, but new data is created every day in every organization.
|
|
#
?
Jun 3, 2015 04:22
|
|
|
Weird question, and I'm having a real tough time making it short. Long story short, I'm buried. We're going through multiple mergers. People are leaving left and right. Officially I am a senior systems engineer. Primarily brought on as an AIX administrator 4 years ago, but that amounts to maybe 10% of my time and is not high maintenance. Vast majority of my time spent on application administration, SAML federation, fax servers, SAP BusinessObjects, lately cutting SQL for some reason. I have virtually no backup for support on our team. Our team is primarily full of windows engineers. IMO our team is big. Bigger than it needs to be if the vision for our team is just building servers and maintaining infrastructure. The reality is we do a lot more than that. We have two "application" teams, one is a new team forming under new management, and an existing one under old management. The existing one is trying to have me divest some of my application responsibilities to them. I'm a bit torn on this. If I divest all of my application responsibilities, that leaves me really with just AIX duties. But at the same time I should have backup. I would actually love to move out of system administration and to applications, I think. It's where my strengths lie, outside of AIX\Linux administration which unfortunately is such a tiny part of what I do. But I fear for the longevity of that team considering the parallel team being created under new management. Right now I am already under new management. So they booked a meeting with me tomorrow to discuss. I think I'll just be straight - maybe all the tickets should go to their queue, but I want access to their queue, and I don't want to divest all responsibility, because really that would be handing off most of my job. But organizationally we need more than one person now to handle this stuff. tldr: Don't want to give up 80% of my responsibilities to a new team, but at the same time need help due to volume of workload. Not sure I want to be under that team because of politics, old management vs new, unless it's that or get out. SSH IT ZOMBIE fucked around with this message at 04:42 on Jun 3, 2015 |
|
#
?
Jun 3, 2015 04:33
|
|
|
Zero VGS posted:Right, so I mean if it turns out we're not getting litigated, I should look into a short email retention time, and prevent archiving? For purposes of conserving local storage and bandwidth, of course. There is no way in hell I would create a legal retention policy that wasn't just a carbon copy of a document that a lawyer drafted and signed.
|
|
#
?
Jun 3, 2015 04:36
|
|
|
Putting in my notice tomorrow. I'm nervous. Not if I'm making the right decision, just about how the actual resignation is going to go. I went with two weeks after my vacation as my last day. I'm fairly confident they'll just say ok but I've never gone through one of these.
|
|
#
?
Jun 3, 2015 05:08
|
|
|
Inspector_666 posted:There is no way in hell I would create a legal retention policy that wasn't just a carbon copy of a document that a lawyer drafted and signed.
|
|
#
?
Jun 3, 2015 05:16
|
|
|
Wizard of the Deep posted:Yup, the 7 years was only meant as a general/best-practices discussion. One place I worked several years back had to keep certain records for at least 60 years for certain civil projects, if it related to design or construction. if you are sure, talk to the lawyer anyway.
|
|
#
?
Jun 3, 2015 08:42
|
|
|
KennyTheFish posted:if you are sure, talk to the lawyer anyway. Yea, in this case when I say "sure", I mean in Inspector_666's sense: A mimeographed policy produced by a lawyer.
|
|
#
?
Jun 3, 2015 12:31
|
|
|
myron cope posted:Putting in my notice tomorrow. I'm nervous. Not if I'm making the right decision, just about how the actual resignation is going to go. I went with two weeks after my vacation as my last day. I'm fairly confident they'll just say ok but I've never gone through one of these. Wgats the worst that will happen, they ask you to stay the two weeks? If they tell you to leave now will it really matter? Goon luck.
|
|
#
?
Jun 3, 2015 13:43
|
|
|
Dr. Arbitrary posted:Anything you save is a legal liability. This. I worked for a few small trading firms, and they made sure that they maintained archives to the specific letter of the law and not a second more. A few times I asked why they don't want to save things longer, and the compliance guy just laughed at me. The point is that you are not saving stuff to use yourself, it's being saved incase someone needs to use it against you, so why save more than what the bare minimum requirement is?
|
|
#
?
Jun 3, 2015 15:35
|
|
|
adorai posted:My followup to that is, are you a member of management or a member of the staff? I make policy decisions regularly, and I don't see how a document retention policy is any different than any other. You need to be informed of the needs of the business and empowered to make decisions that the business will follow. Part of that is having guidance from other parts of the business, including legal, but that doesn't require a signed and notarized statement from the corporate legal counsel. I'm not saying you should throw your hands up and refuse to do anything without legal counsel, but I would not feel comfortable with making that call without at least a signed-off proposal.
|
|
#
?
Jun 3, 2015 16:00
|
|
|
Quick question. Does anyone know of a way to suppress the slmgr -ato dialog box when activating windows in a corporate environment? The network analyst is being lazy (AKA: end of school, slammed here, slammed with whatever class he's taking, seems to be Project Management related), and hasn't updated the images to make the image install completely unattended. The only problem I have with my mini script is the slmgr dialog box causes the script to pause until you close it.
|
|
#
?
Jun 3, 2015 16:36
|
|
|
question, has anyone ever tried to use ansible to do web stuff? I mean, advanced bits that might require more than just curl? Maybe through a selenium module or something? I've got to write an installer and installing rpms and munging config files is no problem, but the only way to add new servers to the overall app is by a ui webpage. Ugh.
|
|
#
?
Jun 3, 2015 17:30
|
|
|
Gothmog1065 posted:Quick question. Does anyone know of a way to suppress the slmgr -ato dialog box when activating windows in a corporate environment? The network analyst is being lazy (AKA: end of school, slammed here, slammed with whatever class he's taking, seems to be Project Management related), and hasn't updated the images to make the image install completely unattended. The only problem I have with my mini script is the slmgr dialog box causes the script to pause until you close it. Call it using cscript.exe ( cscript slmgr.vbs /ato ) it will force a command prompt with text output that will self close.
|
|
#
?
Jun 3, 2015 18:20
|
|
|
EoRaptor posted:Call it using cscript.exe ( cscript slmgr.vbs /ato ) I think you have to have a -nologo in that command line as well or you'll see an annoying pop-up that forces you to click OK or something.
|
|
#
?
Jun 3, 2015 18:31
|
|
|
myron cope posted:Putting in my notice tomorrow. I'm nervous. Not if I'm making the right decision, just about how the actual resignation is going to go. I went with two weeks after my vacation as my last day. I'm fairly confident they'll just say ok but I've never gone through one of these. There's basically two possible outcomes, unless your boss is that sociopath the Australian goon-in-a-well was escaping last month. 1) "ok" 2) "ok. security will now escort you to the door, thanks for your service" Neither one is something to worry about. GL on your 
Docjowles fucked around with this message at 18:47 on Jun 3, 2015 |
|
#
?
Jun 3, 2015 18:44
|
|
|
crunk dork posted:Anyone here ever work for Expedient? Made it through the phone screen and it sounds like an awesome place to get in. In person interview tomorrow. Worked for them. What market? OSC?
|
|
#
?
Jun 3, 2015 19:26
|
|
|
Pissing me off today: job applications that require a numerical value in a last salary field in order to continue. Couldn't put in "My salary is not releasable, per an NDA" so I just put in 999999999999.
|
|
#
?
Jun 3, 2015 20:19
|
|
|
OmniCorp posted:Worked for them. What market? OSC? Indianapolis and yeah OSC. Just interviewed for an analyst spot and it seemed pretty cool. One of the regional managers was in town and sat in with the hiring manager for my interview, hit it off with them pretty well. They had me do this anagram out of box type exercise thing where I had to see how many words I could spell with the word Continental, I got 21 and thought I did bad but apparently that's like twice as good as the next person did. Guess playing word whomp a lot when I was younger paid off. 
|
|
#
?
Jun 3, 2015 20:20
|
|
|
Send help! I've been put in charge of building a website for the new division of my company (which I will generally also be running). I have very minor web development experience (i.e: I can use Google to help me stumble my way through a basic PHP script or whatever). Everything right now is on a VPS running Ubuntu with Apache and PHP (and not much else). I'm busy putting together pretty much everything for what amounts to a new business, so I need this to come together quickly and simply with as small of a learning curve as possible. It also needs to be easy to update and maintain by (hopefully) someone other than me when we can afford things like "employees" and "doing it the right way." Also, due to the aforementioned busyness, my patching policy is going to be along the lines of "If something REALLY critical needs a patch, I will find 5 minutes to SSH in and apt-get the update. Eventually. Maybe." With that in mind, what CMS should I build this sucker on? I need to be able to add new pages for products, update collateral, and have a system for registering accounts to access private pages relating to said accounts' business. I have about 20-30 man hours to go from zero to fully functional. I've worked for enough mature companies to know that whatever I decide here will have consequences 10 years from now that I have no way of foreseeing. If you've ever wondered how lovely legacy systems get to where they are, welcome to the ground loving floor!
|
|
#
?
Jun 3, 2015 20:53
|
|
|
crunk dork posted:Anyone here ever work for Expedient? Made it through the phone screen and it sounds like an awesome place to get in. In person interview tomorrow. I haven't worked for them, but I've yet to work for someone in the area that hasn't done business with them one way or another. Stand up org as far as I can tell from the outside. No major complaints. I would say a good 60% of the IT professionals in Pittsburgh have either worked for Expedient or it's predecessor Stargate at some point in time over the last 15 years.
|
|
#
?
Jun 3, 2015 20:53
|
|
|
Docjowles posted:There's basically two possible outcomes, unless your boss is that sociopath the Australian goon-in-a-well was escaping last month. It actually was #1, but with "oh you know I'm going to have to drag you to a meeting with <CIO> about this". That meeting never happened. They're not going to fire me, they don't have the personnel for that. It is nice that my give-a-gently caress-ometer has dropped. I'm still going to work and doing work there, just the stuff that has been bothering me suddenly doesn't seem so bothersome anymore. Feels good.
|
|
#
?
Jun 4, 2015 00:55
|
|
|
crunk dork posted:Indianapolis and yeah OSC. I never visited Indianapolis when I was there. It was running autonomously under the nFrame name for a while after they acquired it. It's an excellent start for Data Center networking/server/storage/VM. I left after they changed their insurance plan to high deductible and wanted to move on-call to every third week instead of sixth. The have also moved away from the ISP and metro networks business which I enjoyed working on the most. I started in dial-up phone support and was able to move to a Senior Network position in 5 years.
|
|
#
?
Jun 4, 2015 00:57
|
|
|
Question for the thread, Does anyone have general rules of thumb when it comes to disagreements among peers? Yes, this is vague but I'm leaving it as such and I'm a little curious as to everyone's thoughts.
|
|
#
?
Jun 4, 2015 03:50
|
|
|
Tab8715 posted:Question for the thread, Hash it out with the team, hopefully you an come to a consensus?
|
|
#
?
Jun 4, 2015 03:55
|
|
|
Tab8715 posted:Question for the thread, Be respectful, calm, patient, empathetic, admit if/when you're wrong, etc. Normal mature adult stuff.
|
|
#
?
Jun 4, 2015 03:58
|
|
|
Tab8715 posted:Question for the thread, Rockem Sockem Robots.
|
|
#
?
Jun 4, 2015 04:02
|
|
|
Let the other side of the argument win and then rub it in their faces non-stop when any situation comes up where your suggestion was better.
|
|
#
?
Jun 4, 2015 04:05
|
|
|
|
| # ? Apr 24, 2024 18:25 |
|
|
CLAM DOWN posted:Be respectful, calm, patient, empathetic, admit if/when you're wrong, etc. Normal mature adult stuff. I was of the assumption this would occur the further I go into my career. AreWeDrunkYet posted:Hash it out with the team, hopefully you an come to a consensus? Lets say you can't come to a consensus and someone says they'll test it themselves. Is this wrong or remotely offensive?
|
|
#
?
Jun 4, 2015 04:50
|
|