Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Shoelayceberry the [Unlaced]

Pages: [1] 2 3 4 5 6 ... 651
General Discussion / Re: Theory posted to XKCD
« on: January 30, 2015, 12:19:50 AM »
good on you for having the balls to do it. failure is the crucible to greatness.

Spamalot / Re: my body hurts
« on: January 29, 2015, 05:20:29 PM »
makes sense

General Discussion / Re: 17 year old girl killed by cops in Texas
« on: January 29, 2015, 04:54:58 PM »
So sad man.  Shit went on for like 15 minutes.  None of them had mace or a tazer?  None of them could have gotten to one of those either in their car right outside or from the actual police station?  Shrug.

read a quick brief that said there was a tazer attempt. Didn't affect her.

Spamalot / Re: my body hurts
« on: January 29, 2015, 04:47:18 PM »
Did not know about the MS.

Spamalot / Re: JET interview in 1 hour
« on: January 29, 2015, 04:40:50 PM »
good luck

Spamalot / Re: That's enough internet for today.
« on: January 29, 2015, 12:10:47 AM »
between this and the woman in post partum, on meds, slitting the throats of her 2yo and twin 6mo's to "quiet them down" pretty much began a spiral down today.

Spamalot / Re: New Ghostbusters cast
« on: January 28, 2015, 11:47:08 PM »
Egon died in 2014 kids

General Discussion / Re: Pleenq -- My New Startup
« on: January 28, 2015, 09:22:04 AM »
when does the new season start? Loved that show.

General Discussion / Re: Pleenq -- My New Startup
« on: January 27, 2015, 02:45:40 PM »
this is actually a monetization model

I picked that up. I don't think I understood how you or they make money, but it's a damn powerful idea. You really could make a metric fuckton of money if you can grab some decent market early. The big boys would have to buy you out then and I doubt it would be cheap. Grats man.

General Discussion / Re: Fais Vase
« on: January 26, 2015, 11:56:17 PM »

Spamalot / Re: I know you guys think I'm crazy
« on: January 22, 2015, 03:38:16 PM »
It will look like gibberish to anyone who doesn't know their shit.

A quote like that would most likely result in being dismissed, especially if anyone were to know that you have no formal training in either Math or Physics.

That doesn't mean it's not true, but it would be hard to take anyone seriously under those circumstances. I think Reddit may be a good idea, if nothing else, than to see if you really understand what you think you do under questioning. I also haven't looked at all the final edits, due to needing time to digest technical/theory writing.

I believe reboots to be used in series, both movie and TV, whereas remake would be used for stand-alones and therefore mostly/always in movies.

Tech Heads / Re: Exchange Admins?
« on: January 21, 2015, 09:10:00 PM »
Absolutely. Now that I understand most of whats going on, it's that itch you can't scratch. This will get solved this this year, either by storage upgrades, allowing our backups to process more/faster, or we are about to stand up a temporary SystemCenter DPM server as a secondary backup solution to keep log files truncated, or a migration to 365.

It's just that I find Failover Cluster info for generic services as the most google hits, which is fine, but I need solutions specifically for what we have and you will only see this in Exchange 2003 or 2007, as 2010/2013 moved to DAGs, which are different. And, we may already be doing it correctly, but I was wondering that if we caught the logs filling up, but didn't have time to run a backup, what is the best practice way to trim those log files without potentially losing data.

What I have been doing with my documentation is linking info to all relevant source material, so no one has to do this again, and making a quick and dirty "cheat sheet" for how to handle/troubleshoot any issues, particularly DB issues, since that is what occurs with log file truncation problems.

Tech Heads / Re: Exchange Admins?
« on: January 21, 2015, 07:52:51 PM »
sorry for any misunderstanding, as we have jumped around a bit, but the main issue is proper Failover Cluster management, for the exchange db cluster, to clear log files, either before (hopefully) or after a failure (fill up of log drive). The procedure we use, mentioned above, seems to create more work. Maybe that's the only way you can do it, but I was hoping there was a step or two we are missing, to prevent reseeding.

Tech Heads / Re: Exchange Admins?
« on: January 21, 2015, 06:04:48 PM »
Yes I have.

We merged and had too many IT people, for sure. I bit the bullet, since I wasn't native to the home office city anyway, and took the San Diego gig before I got cut.

In the last 10 years our main profit making machine disappeared. Gene Sequencer technology has progressed faster than Moore's Law. I have a shirt, from just joining the Institute, celebrating our first millionth lane sequenced; it took ~3 years IIRC. We were one of the largest privately owned gene sequencing centers in the world, 12 rows of 10 sequencers, online 24/7/365, worth $100 million. That was probably a team of 25ish lab techs, just running the sequencers, and probably another 25 other lab tech support in the building. We had a warehouse style building supporting all this and one Admin positioned over there every day, that just supported that building.

We helped track down the "white powder" being mailed to Congress after 9/11. We've been called in to assist with the Bird Flu that came through a few years ago. Numerous other incidents. Now, however, there's a single machine just moved into my lab area, that does a million lanes in 2 days; the price tag is somewhere between $500k-$1 million.

We're near the center of the Big Data revolution and having to radically change how we do business. Automation will be key to how we do business in the future, and I have been doing my part over the last 5 years to get us there, but with the knowledge that we may be downsizing, they are hesitant to hire more support staff to keep up with what we have. Only they have asked for more items to come online, mostly due the President (who has never gotten along with IT, and is fairly inept with it) and her brother (who is almost just as bad). As things wind down, there will no longer be a place for the brother and he will bail. Hopefully she will soon thereafter; she's a very good scientist and works with the Human Microbiome project a lot. Once their out the door, there will be more support. I am hoping to outlast that, but before I go, if I go, I will make sure that CEO knows why. He may even relocate me elsewhere, as he is pretty good at taking care of people who take care of him.

Tech Heads / Re: Exchange Admins?
« on: January 21, 2015, 05:22:31 PM »
Also, I appreciate the sentiment, and was on the cusp of getting everything ready to leave mentally, but I promised my VP, who hired me, I would stay for the short term. He has been voted out over and over on these issues by the President and her brother the Project Manager of the Institute. He (the brother) has been the driving force of all the updates/upgrades and new services we have been doing, that essentially forced my Senior admin to leave, by having all of this dumped on him.

Recently there was a shakedown and CEO found out about some things, so the VP has been taken more serious lately. The real deal is we may be a single site office in 2 years; maybe less, maybe more. We'll also probably attempt to dump everything to the cloud, then find out you shouldn't dump everything to the cloud, and be able to staff yup again. Once that happens, I will be in position to move up in management. I will also be in a position to dictate "fix this or I walk" and there will be no other people in the business to pick up the torch. At worst I would get a fat package to remain available for help as I move elsewhere, to certainly better pay, but maybe a shittier place. If I manage to stay past all that, I would be able to dictate the hiring of consultants as I will remind them they gutted staff before a solution was present and with such a varied environment, no one person knows all the pieces. Either hire a consultant or it doesn't get done.

In the meantime, I keep consolidating and documenting my work, posting to LinkedIn, and once or twice a month get pinged by headhunters asking if I will bail. Once I get my Linux skills back up later this year, I will be a triple threat, that may be able to consult full time, if I wanted to, though I would probably take another drone job unless Utumno hooked me up with some new outta site Mashable startup.  :evil:

Tech Heads / Re: Exchange Admins?
« on: January 21, 2015, 05:03:54 PM »

We are already federated and have been able to migrate test mailboxes back and forth. The Senior Admin even had his box there for a while. Question on those migrations: my Boss tried to copy a mailbox over last week; a small one, though I don't remember how big, and he said it took forever. Did y'all see this?

^ yup

I didn't get it until 16, even after my parents did the "go play with johnny (who has chicken pox)" thing. It was horrible. literally covered head to toe, including balls(!) and sores on my tongue(!). I also rocked a 105 fever/partial delirium and had to crawl to my parents room where they put me in a cold tub to cool off. Pretty scary.

Spamalot / Re: I am OK now
« on: January 20, 2015, 11:43:56 PM »
i feel like we need some marley up in here

Tech Heads / Re: Exchange Admins?
« on: January 20, 2015, 08:34:56 PM »
The good answer is that I am safe all the way up to VP of IT, because they are/were techs in the field. I could even -maybe- bring something up with Dr. Venter if I thought it was a disaster situation, but only if the chain of command failed. It's not failing here. We ARE moving to Office 365, but we're stuck where we are until we (me) can migrate; we were waiting for some other legacy apps to get updated and they are almost done. We are also waiting on delivery and deployment of new storage and backup server. Basically every piece of this puzzle has a fix in the works, but in the meantime an email outage can occur multiple times a week, unless the backups work.

In the meantime, knowing Exchange is a valuable skill that is dying off - potentially leading to lucrative contract work if there's ever a need. The problem is that instead of a hand-holding migration with my Senior Admin, he left me holding the hot potato when he got a new job. My immediate supervisor has older exchange background, but he let our Senior guy handle it after our merger, so he is very rusty. There is a huge difference between book knowledge and true support knowledge in the field, so I am having to earn it the hard way. As always, it came at a bad time. I am finally catching up, by getting some documentation done, putting myself more at ease.

It's just that while I am doing the above, I am also doing:

1) OSX is on a quick release cycle and our current deployment methods need to be tested, and after today, probably upgraded.

2) I need to rebuild my Altiris validation environment, then move to production; our production environment in the main office will no longer work with our newer machines for imaging and I had it working out here, before I pulled a bonehead maneuver and applied a hotfix incorrectly. It was suggested I rebuild, but that happened right when the Senior Admin left.

3) Our antivirus server is 2003 which goes out of support in June. Our VMware is only running 5.0 and we introduced a bug for Server 2012 with the last update. So, I got that figured out and now need to migrate to the new server. After the SSH and SSL vulnerabilities last year, I really need to upgrade this and when I last tried, the upgrade FUBARed the server to the point that I had to deploy from backup snapshot. This is next highest priority after Exchange.

4) 77 legacy 2003 servers need to be condemned or migrated to newer OSes, due to the aforementioned EOL for Server 2003 this year.

5) Implement AD Account Auditing for the important groups, which is very basic and won't take long, but I also need to get our Macs up to date with logging as well. The Macs are still in early testing phases. This is important for FISMA that determines what grants we can apply for. As money topic this gets done after Exchange and Symantec.

6) Other things on a list of "Nice to Haves"

Plus, still handle day-to-day helpdesk support. The constant interruptions here are killing me. There was some talk of making me a team lead and hiring another helpdesk person on my coast, which would help, but it will also require me getting dirty training the new person. I also haven't heard anything about this in a month or two, so we'll see.

Tech Heads / Re: Kamara, Cry me a river of SQL suggestions...
« on: January 20, 2015, 05:02:53 PM »
Bumping this for some point in the future. I forgot there was a book mentioned, so I bought my own, based on an IIS book I recently picked up:

Learn SQL Server Administration in a Month of Lunches

Will try to remember to review it at some point, after I have read and used it.

Tech Heads / Exchange Admins?
« on: January 20, 2015, 04:57:40 PM »
Long shot, but looking for some guidance. Maintenance/recovery question...

We will eventually migrate off of this, to Office 365, but in the meantime I have inherited an Exchange 2007 environment, with 2 Hub/CAS servers in an NLB, and a CCR Failover Cluster. All server OSes are Server 2008. All servers are running all latest patches and Exchange rollups. We have 25 Storage Groups, each containing a single DB. On the Mailbox server cluster, we have separate filesystems for logs and DBs. This is all virtual in VMware 5.0 (very behind here too).

The admin I inherited this from had started a test phase with O365 by setting up a 3rd Hub/CAS server with Exchange 2010 (Server 2008 R2, patched and Exchange rollups all the way).

Everything is running great with Exchange. The problem is our backup software (Netbackup) is out of date and backup hardware is taxed. So, the occasional backup fails. This causes our log drive to fill, causing Exchange to stop sending mail. We had no monitoring solution that I know of, so during the last couple of months, I have been documenting everything (for my own sake, to learn how everything works) and getting these upgrades done, including getting PowerShell v2 on all nodes. This all should be finished in the next couple of days. My plan is to setup a repeating PowerShell script to monitor drive fullness that will email me nightly, and my boss weekly; eventually this (or similar) will be deployed to all critical servers. 2 Things:

1) What else should I be doing? I had just taken a class early last year, for Exchange 2013, but that has been little help in a production environment of 2007; almost everything has changed. I have mostly read an Exchange 2007 book, so along with my 2013 reading, I have a feel for how everything should work. I expanded on that with the documentation, which we had 0 of, so that I know all points of failure. Still needing to trace mail flow from OWA (and other web services), as I think that may be hosted on the "new" 2010 box as there was recently a disruption after my boss patched it; (re)starting some services on that box brought everything back online.

2) CCR Failover Cluster. What is the proper way to recover from our full log drive? It seems we have to reseed the passive node every time we recover. I think we may be causing that ourselves. Current steps are:

a) Dismount-Database -Identity dbname
b) eseutil /mh "path_to_db.edb"
c) assumung state = clean shutdown, delete all logs on largest Storage Groups\DBs  <THIS MIGHT BE POTENTIAL SPOT OF FAILURE>
d) Mount-Database -Identity dbname

DBs come back healthy, but CCR maintains an initializing state for as long as we let it, then we reseed (Update-StorageGroupCopy -Identity dbname) which eventually gets everyone back in a happy copy state, in case of failover.

Since I inherited my new role back in ~August last year, I have been in a state of perpetual fear and failure making life in-general stressful. I am happy that I have my new responsibilities, as I know after I master this I will have experience with all major Windows Enterprise technologies: NLBs, Failover Clusters, Exchange Support, IIS, Basic Database work (I have another project I was working on requiring MS SQL, but that has been on the backburner due to this), but it has been a bad way to learn - maybe this is how everyone does it? Anyway, I have been pretty burnt out for about a year now, due to previous posts I have made about moving buildings, so once this gets handled in a way that I am happy with, I can relax a bit, then pick back up on my other task and learn some SQL.

Any help would be appreciated. Thanks.

General Discussion / Re: Posters you want to see come back
« on: January 19, 2015, 11:05:45 PM »
and who was that dark elf necro... "tinyman, TINYMAN!"

Soulslam and Bruce, sharing KungFu across Norrath

Getting Fat with TZT / Re: Healthy Choices
« on: January 19, 2015, 10:44:25 PM »
gumbo is all about the roux my friend.

Getting Fat with TZT / Re: Healthy Choices
« on: January 17, 2015, 12:37:51 AM »
it would work, just longer cook time. Don't know how true it is, though I always try to follow it, but the goal is to never open your pan/pot until the rice is cooked. Here's another one I just did last weekend:

Shrimp-and-Sausage Jambalaya
2 tablespoons vegetable oil
1 pound andouille or other spicy smoked sausage, sliced
1 large onion, diced
1 bell pepper, diced
3 celery ribs, chopped
4 garlic cloves, minced
2 bay leaves
1 teaspoon dried thyme
1 teaspoon dried oregano
2 teaspoons Creole seasoning
1 (28-ounce) can crushed tomatoes, with juice (OPTIONAL)
4 cups chicken broth
2 cups uncooked long-grain rice
1 pound shrimp, peeled and deveined
4 green onions, chopped

1. Heat oil in a Dutch oven over medium-high heat. Add sausage, and cook, stirring constantly, 5 minutes or until lightly browned. Remove sausage with a slotted spoon; set aside.

2. Add onion and next 7 ingredients to hot drippings in Dutch oven; sauté 5 minutes or until vegetables are tender. Stir in reserved sausage, tomatoes, broth, and rice. Bring mixture to a boil, reduce heat, and simmer, covered, 25 minutes or until rice is tender.

3. Stir in shrimp; cover and cook 5 minutes or until done. Sprinkle each serving with green onions.

I actually cut the heat just before step 3, then added the shrimp and stirred in, 2 separate times over 5 minutes. That should be plenty to cook the shrimp. Overdone shrimp is the worst and it is the most obvious thing I run across while eating out on the reg. As a Louisiana boy it pisses me off. Cooking it as above, with cut heat, will allow you to reheat the shrimp dish without overcooking. Oh, I would say that more than "lightly" browning the sausage is key. You want those brown bit to be available, especially when dealing with nonstick pans like I do.

Spamalot / Re: got free bottle service and i only had one job
« on: January 16, 2015, 12:39:21 AM »
man up and lance that shit dude

General Discussion / Re: snowboarder causes avalanche
« on: January 16, 2015, 12:10:31 AM »
video shockingly uninteresting

will work at implementing i'm talking about mountain dews baby into my luxicon

Tech Heads / Re: stuck with windows 8
« on: January 09, 2015, 06:06:54 PM »

now we're starting to get good advice

Pages: [1] 2 3 4 5 6 ... 651