The "won't sync" issue is not unique to Blackberry devices; I've seen the same issue with Android devices and iPhones, albeit much, much less often. Popping the battery out usually helps with Android phones, though you can't do that with an iPhone - you need to completely remove the account info, power down the device, then enter the account info back in before the ActiveSync connection can be reestablished.
I've worked IT for a health organization before. They're probably mandating this because whatever they've implemented to comply with HIPAA and/or other regulations is dependent on AD and Group Policy. I can tell you from experience that if you're operating on a limited budget and are already running and AD/Exchange environment, you don't have to spend any extra money to become HIPAA compliant. However, that does lock you in to using MS products, since they're the only ones (easily) supported by GP. Could other operating systems and software be introduced and still be compliant? Of course, but that would add administrative overhead supporting and auditing those systems and applications that fall outside control of your AD/GP domain.
Ok, lets be fair. If you're going to compare Gmail to Exchange, at least compare it to an Exchange implementation of similar scale - such as Hotmail. A cursory search turned up an outage from March and one from earlier this month.
The car analogy doesn't work here, yet again. I've seen what happens when someone leaves the keys in a car, puts a sign on it that says "Take Me." Nothing. That's what happens. No one touches the damn thing.
A friend of mine did just that, as well as place the title on the dash, in an attempt to get rid of the pos. This was at least 10 years ago, so no CARS program, and he was too lazy to do much else with it. Our theory was that he made it too easy, that anyone who would potentially acquire a car by such means would be too suspicious. That, or it was such a pile that not even potential car thieves would touch it.
Any place I've worked at, I've always advocated using utility-based naming schemes, prefixed with the org's abbreviated name, e.g. xyz-mail01. As systems needed replacing, I've migrated many places to such a scheme, usually from theme-based or other similar nonsensical systems. It just looks more professional and is easier to become acclimated to as new staff arrives.
At home, however, I use the Cthulhu Mythos as a naming theme. I posted this from my laptop, Byakhee. Nonsensical, yes, but it keeps me amused.
This sounds like the headache I went through implementing HIPAA policies where I work. My first thought and recommendation was PGP. It's widely used and you only have to do the key exchange once per contact. Plus, it was a hell of a lot better than what they were using before, which were password-protected Excel sheets.
However, training our staff proved difficult, they kept getting hung up on the key exchange, even though they were reminded that it was only necessary to do this once per contact, and they would be assisted in this process. The other difficulty was partners and consultants were unwilling or unable to implement PGP (or something compatible) on their end.
Since PGP seemed too complex for the HR crowd, I tried implementing something that would be a bit simpler, and mirror their current process: encrypted zip files. Kludgy and ugly, but it fulfills HIPAA requirements (secure transport). Winzip is familiar and easy for them to use, and supports 256bit AES encryption. Before they send sensitive material, they call the recipient first to share the password, then send the data.
You don't 'become' a yuppie in the same way that you become a parent bringing the kids out to dinner. Actually, you kinda do. I think you're confusing the slang definition of yuppie with its actual meaning. Your market demographic changes as you become gainfully employed (Yuppie), get married (DINK), and have kids (parent bringing the kids out to dinner). That's the point Parent was trying to make...
It's just not funny anymore once you have to explain it.
Strange, all my broken clocks are correct twice a day. Do you do out of your way to purchase 24-hour clocks and break them? I thought my hobbies were weird....
Don't worry, according to the task force for 10GBASE-T (IEEE 802.3an), cat6 can support 10Gbit up to 55m. The proposed cat6a will support it out to the usual 300m.
And I'm not vulnerable. Don't be so sure. The first time I ran it, it dropped me into root. However, I decided to run it a second time, and I got a segfault. Third time, it gave me a "wtf." I had to run it about a dozen more time before it dropped me into root again. Run it a few more times, just to be sure. It is just proof-of-concept code, after all.
My little brother got his arm stuck in the microwave. So my mom had to take him to the hospital. My grandma dropped acid this morning, and she freaked out. She hijacked a bus-load of penguins. So it's sort of a family crisis. Bye!
*slams door*
Zimbra and OpenXchange to name a couple. I looked into this a couple of years ago, and there were about a half a dozen or so at the time, each with varying degrees of success of duplicating Exchange's features. Looks like Zimbra is the current leader, and now that they're under new ownership with more capital, hopefully they'll continue to get better.
Oh, if I only had Mod points. RT is great. Once you get used to it, it's not too difficult to customize, and can be extended with the user-contributed modules (e.g. LDAP/Active Directory integration). There's even an O'Reilly book that outlines customization for different requirements/environments.
Wow, I followed almost the same progression as you, and came to a similar conclusion. The last FF I played was 8, and the last one I truly enjoyed was 7. Sometimes I play the original for nostalgia, but I'd have to say 6 is my overall favorite. I've always been a pen-and-paper RPGer, so these games passed the time between campaigns for me. They had compelling storylines, but recently they've become repetitive and stale.
Yes, because we all know how reliable that can be. It will only try to restart the service 3 times, in quick succession, then give up. Or, how about my other example, when the service locks the system by monopolizing CPU time? The service hasn't technically stopped, but it's not doing what it's supposed to, so you still have to rely on users to tell you what's wrong.
Would you prefer a different example? Nagios can check a URL, looking for a particular string (like something from the main page of a web app). If it doesn't return the proper result (like it lost the connection to the database, or it's being DDoS'd, etc.), the service or daemon responsible can be reinitialized, or start a backup process, etc.
Oh, and Nagios will email or SMS the on-call person during all this.
I thoroughly enjoy the event handler capabilities built into Nagios. Just that single feature has made my day to day administrative tasks easier, and well worth the hours to write the scripts and get it all configured properly. For example, it's so nice to have the spooler service on a win32 box restart automatically if it has locked or died unexpectedly, and not have to wait for the calls to come in when users can't print.
Slashdot Mirror
The "won't sync" issue is not unique to Blackberry devices; I've seen the same issue with Android devices and iPhones, albeit much, much less often. Popping the battery out usually helps with Android phones, though you can't do that with an iPhone - you need to completely remove the account info, power down the device, then enter the account info back in before the ActiveSync connection can be reestablished.
It's no joke. And stop calling me Shirley.
I've worked IT for a health organization before. They're probably mandating this because whatever they've implemented to comply with HIPAA and/or other regulations is dependent on AD and Group Policy. I can tell you from experience that if you're operating on a limited budget and are already running and AD/Exchange environment, you don't have to spend any extra money to become HIPAA compliant. However, that does lock you in to using MS products, since they're the only ones (easily) supported by GP. Could other operating systems and software be introduced and still be compliant? Of course, but that would add administrative overhead supporting and auditing those systems and applications that fall outside control of your AD/GP domain.
Ok, lets be fair. If you're going to compare Gmail to Exchange, at least compare it to an Exchange implementation of similar scale - such as Hotmail. A cursory search turned up an outage from March and one from earlier this month.
The car analogy doesn't work here, yet again. I've seen what happens when someone leaves the keys in a car, puts a sign on it that says "Take Me." Nothing. That's what happens. No one touches the damn thing.
A friend of mine did just that, as well as place the title on the dash, in an attempt to get rid of the pos. This was at least 10 years ago, so no CARS program, and he was too lazy to do much else with it. Our theory was that he made it too easy, that anyone who would potentially acquire a car by such means would be too suspicious. That, or it was such a pile that not even potential car thieves would touch it.
In the second image: /. has a Wave account. Well, anyone that matters on Slashdot has a Wave account."
:(
"Everyone on
If you're already using Nagios, migration to Opsview is extremely smooth.
Do not untwist the pairs any more than necessary.
Make sure the outer jacket is inserted into the end of the RJ-45 connector.
I can't explain how frustrating it is when I see this in wiring closets. It's no wonder that the entire IT staff before me was fired.
You must be new here.
Oh my, it's the rebirth of a meme...
Any place I've worked at, I've always advocated using utility-based naming schemes, prefixed with the org's abbreviated name, e.g. xyz-mail01. As systems needed replacing, I've migrated many places to such a scheme, usually from theme-based or other similar nonsensical systems. It just looks more professional and is easier to become acclimated to as new staff arrives.
At home, however, I use the Cthulhu Mythos as a naming theme. I posted this from my laptop, Byakhee. Nonsensical, yes, but it keeps me amused.
However, training our staff proved difficult, they kept getting hung up on the key exchange, even though they were reminded that it was only necessary to do this once per contact, and they would be assisted in this process. The other difficulty was partners and consultants were unwilling or unable to implement PGP (or something compatible) on their end.
Since PGP seemed too complex for the HR crowd, I tried implementing something that would be a bit simpler, and mirror their current process: encrypted zip files. Kludgy and ugly, but it fulfills HIPAA requirements (secure transport). Winzip is familiar and easy for them to use, and supports 256bit AES encryption. Before they send sensitive material, they call the recipient first to share the password, then send the data.
Well, if we're talking about Windows Mobile, Exchange and ActiveSync, then all 3 need to be updated, naturally.
It's just not funny anymore once you have to explain it.
Strange, all my broken clocks are correct twice a day. Do you do out of your way to purchase 24-hour clocks and break them? I thought my hobbies were weird....
Don't worry, according to the task force for 10GBASE-T (IEEE 802.3an), cat6 can support 10Gbit up to 55m. The proposed cat6a will support it out to the usual 300m.
... I compiled it and ran it.And I'm not vulnerable. Don't be so sure. The first time I ran it, it dropped me into root. However, I decided to run it a second time, and I got a segfault. Third time, it gave me a "wtf." I had to run it about a dozen more time before it dropped me into root again. Run it a few more times, just to be sure. It is just proof-of-concept code, after all.
My little brother got his arm stuck in the microwave. So my mom had to take him to the hospital. My grandma dropped acid this morning, and she freaked out. She hijacked a bus-load of penguins. So it's sort of a family crisis. Bye! *slams door*
Sorry Johnny, I don't have a dime.
What's so bad about being a hunter?
Zimbra and OpenXchange to name a couple. I looked into this a couple of years ago, and there were about a half a dozen or so at the time, each with varying degrees of success of duplicating Exchange's features. Looks like Zimbra is the current leader, and now that they're under new ownership with more capital, hopefully they'll continue to get better.
Oh, if I only had Mod points. RT is great. Once you get used to it, it's not too difficult to customize, and can be extended with the user-contributed modules (e.g. LDAP/Active Directory integration). There's even an O'Reilly book that outlines customization for different requirements/environments.
...or OSX. The couple of Java devs I know have Macs. I know, this is anecdotal evidence, at best.
Wow, I followed almost the same progression as you, and came to a similar conclusion. The last FF I played was 8, and the last one I truly enjoyed was 7. Sometimes I play the original for nostalgia, but I'd have to say 6 is my overall favorite. I've always been a pen-and-paper RPGer, so these games passed the time between campaigns for me. They had compelling storylines, but recently they've become repetitive and stale.
Yes, because we all know how reliable that can be. It will only try to restart the service 3 times, in quick succession, then give up. Or, how about my other example, when the service locks the system by monopolizing CPU time? The service hasn't technically stopped, but it's not doing what it's supposed to, so you still have to rely on users to tell you what's wrong.
Would you prefer a different example? Nagios can check a URL, looking for a particular string (like something from the main page of a web app). If it doesn't return the proper result (like it lost the connection to the database, or it's being DDoS'd, etc.), the service or daemon responsible can be reinitialized, or start a backup process, etc.
Oh, and Nagios will email or SMS the on-call person during all this.
I thoroughly enjoy the event handler capabilities built into Nagios. Just that single feature has made my day to day administrative tasks easier, and well worth the hours to write the scripts and get it all configured properly.
For example, it's so nice to have the spooler service on a win32 box restart automatically if it has locked or died unexpectedly, and not have to wait for the calls to come in when users can't print.