Sounds like a different setup than what I'm using. I can perform basic operations directly from my workstation, no remote required.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
First world IT problems...
- Thread starter tspinning
- Start date
- Sort by reaction score
Sounds like a different setup than what I'm using. I can perform basic operations directly from my workstation, no remote required.
You are talking about Server Admin Tools which require you to be on the domain or to authenticate with a domain admin. They are just saying you still are using 2 boxes since you need the server running for the admin tools to work on your local machine.
I'm just going to add one more post, then bow out. This has gone quite off topic and neither side is making much progress with the other.
First, PowerShell. If you're not using it (even with Windows on your laptop), I think you should seriously take a look at it.
Consider this: 5 new employees join the company. What do you do? For me, if I didn't use PowerShell, I would do the following steps:
1. Add user into AD Users & Computers
2. Add proper groups to user based on job role and if FTP access is required
3. Log into Sharepoint and grant access based on job role
4. Wait 3 hours for AD to sync with Office 365
5. Use Office 365's web tool to apply an Exchange P2 license and select their origin country
6. <Has to be done in PS - cannot be done with a GUI> Turn on archiving for the new mailbox
7. <Has to be done in PS - cannot be done with a GUI> Apply retention policies to the mailbox
7 steps, 3 hours 15 minutes or so to go through all the GUI screens and websites.
With PowerShell?
1. Connect via SSH to PS
2. Run new user function and fill in first name, last name, domain, job role, location based out of, email domain
2 steps, 70 seconds - 60 seconds of that is waiting for AD to sync with Office 365 since the script does a forced sync.
Now imagine repeating either method for 5 users (or 50 users), which is faster?
I highly recommend moving most of your admin work to PowerShell regardless of your platform. It makes everything you do faster and easier. This was only one example of where it improved work efficiency.
Second, platform agnostic. As an admin, you shouldn't feel like you need to do work on one platform or another because there will come a time when you don't have access to it, a server is down and now what do you do?
My example: A Hyper-V system needs to be reimaged but I'm in China right now (we have many locations there). The time difference is 12 hours. It's noon on the east coast and it is midnight in China. I'm out at a bar shooting pool with expats and I get a call about a Hyper-V machine not working.
Well, I can hail a cab and ride back to the hotel where my laptop is. Or if I have everything configured around remoting with the platform being agnostic, I can whip out my phone (iPhone, Android, <insert smartphone>), connect via VPN to the location in question, SSH to the machine, run the Hyper-V scripts to restore a VM and I'm done in a few minutes. Back to relaxing.
While some companies might have people to back you up, you can't always rely on that. It's good to not worry about what computers are around you for work. Any computer device is good enough for the job. Especially if your own job is on the line when **** hits the fan.
Wow, thanks for the time to respond and evolve the questions and issue here!
I had thought up a few individual responses as I read along, but that got long, anyway I feel I'll be able to do anything I can do today on a Mac for work, including leverage virutalized machines/apps and obviously powershell. I'm primarily a SCOM/System Center Admin so display resolution is important in my use-case. Building reports and multi-window displays and front-ends is tough at anything x 900!
I'll toss in that my last laptop was/is a Lenovo T500 - circa 2009, probably one of the better pieces of hardware I'll ever use, sturdy, great keyboard, powerful, not small
and that makes the issue on my move to Dell vs. Mac one of form/function and quality. I understand a lot of companies get good Dells, I don't argue there aren't a few solid models sold, but I also recall the days of Optiplex desktop motherboards melting capacitors (2006-7) during my desktop time, and again issues with some more current generation laptops.
Anyway, I'll post back around here later regardless as I've now signed up for my passport to Mac.
If all goes well it won't be for another month and a half
I had thought up a few individual responses as I read along, but that got long, anyway I feel I'll be able to do anything I can do today on a Mac for work, including leverage virutalized machines/apps and obviously powershell. I'm primarily a SCOM/System Center Admin so display resolution is important in my use-case. Building reports and multi-window displays and front-ends is tough at anything x 900!
I'll toss in that my last laptop was/is a Lenovo T500 - circa 2009, probably one of the better pieces of hardware I'll ever use, sturdy, great keyboard, powerful, not small
and that makes the issue on my move to Dell vs. Mac one of form/function and quality. I understand a lot of companies get good Dells, I don't argue there aren't a few solid models sold, but I also recall the days of Optiplex desktop motherboards melting capacitors (2006-7) during my desktop time, and again issues with some more current generation laptops.Anyway, I'll post back around here later regardless as I've now signed up for my passport to Mac.
If all goes well it won't be for another month and a half
Last edited:
I must say, it's interesting to see how other IT departments function compared to my own. My needs are much different from yours which could probably explain the difference of opinion about Mac being viable or not.
I'm managing a small subset of users (only about 300) on a hospital network, in a specialized program. A lot of our IT policies and practices centre around confidentiality and patient safety. Many of our tools are Windows only, with no *nix counterparts. Because of the confidentiality issues, there are also strict guidelines on what's available by remote. That's why I was always saying using a Mac would add an extra machine into the mix. In order for me to use those tools from my Mac, I had to remote into my workstation with access to the tools, there was no option of working directly from the Mac. Even then I'm skirting a grey area when it comes to policies.
I think it's fair to say that everyone's situation is unique. Macs for IT admin won't work for everyone, but it seems it can definitely work for some with no extra effort after the initial setup.
As a new IT Admin for a small department at a Major University, this thread has been very educational. I am in a similar situation as the OP and was trying to wait out for the new MBP, but with only 2 weeks left to create a PO, it's getting tough to wait. Current model will probably get ordered, which is fine by me.
The tools, techniques, etc listed in this thread are invaluable. Thanks, everyone, for posting...I hope I'm not the only one that has learned a thing or two.
The tools, techniques, etc listed in this thread are invaluable. Thanks, everyone, for posting...I hope I'm not the only one that has learned a thing or two.
This part pretty much says it all. I completely understand now. I never thought about other sectors with privacy issues - I work for a global manufacturing company.
I can think of a 1000 reasons to chose Apple build quality over any other windows machine.
If OSX continues its downward spiral into the land of iOS my next step is loading Win8 on a mac and just bootcamping it. I'd keep a small OSX partition shell just for updates.
The problem with this approach is you're at Apple's mercy for drivers.
I can think of a 1000 reasons to chose Apple build quality over any other windows machine.
If OSX continues its downward spiral into the land of iOS my next step is loading Win8 on a mac and just bootcamping it. I'd keep a small OSX partition shell just for updates.
The problem with this approach is you're at Apple's mercy for drivers.
I think your 1000 reasons is a bit steep. When it comes to build quality and reliability, there are definitely machines that exceed Apple's standards. Lenovo comes to mind near the top of the list.
Also, with your dislike for the iOS tumours that are growing in OSX, do you really think windows 8 is a better solution?
Nope. Have one, used 'em all. Still creaky and cheesy plastic. (Although it's a breeze to change out parts).
Yes. If there were decent trackpad drivers available. Plus, I guarantee Win8 will be supported 5 years after release. (Unlike the iterations of OSX).
THREE. HOURS. Wow. that doesn't make any freaking sense for microsoft. Heck, Intermedia (who we use) gives us an AD sync tool that syncs every time we make a change.
As I mentioned in the PowerShell section, you can do a forced sync. But no, it doesn't sync automatically each time you make a change. Would be a nice feature.