Windows. Close open Blizzard programs. Press Ctrl+Shift+Esc to open the Task Manager. Click the Processes tab. If agent.exe is running—or Blizzard Update Agent in Windows 10—select it and click End Process. Navigate to the folder containing the cache directory:. Press Windows Key+R to open the Run dialogue.

Type%ProgramData% into the Run field and press Enter. If a Blizzard Entertainment folder exists in the directory, right-click it and select Delete. Restart the Battle.net desktop app and relaunch the game.

I would say it depends on what most people in your organization are using by way of platform (more Mac, or more Windows). If you are mostly Mac (which I am assuming here since you had Open Directory), you might have some pain with moving to AD since there is no native management for Macs aside from the simple ability to join a Mac to an AD domain. If your plan is to switch to Windows on the desktop and server side, than you will only derive benefits from switching to AD. I would make sure that there is a solid business-driven decision to make this change.

In other words, ask the question, 'How will moving to Active Directory help drive our business better than Open Directory does right now?' I have not had anything else so it would be hard to be subjective. I can just list the things I like with Active Directory. Being able to manage users and shares and computers and memberships all from my local computer. On that same line of though being able to reset passwords and unlock accounts from my computer is nice as well. I don't know if LDAP works with any other systems but it does like Active Directory talk to different software so that it can pass account information.

Group policy while its a bugger to learn once you really get to know it you can do so much from one place that will effect all the computers. Changing settings, adding printers, even with some log on scripts you can update software. I wish I had knowledge of any other type of system. Well I mean I kinda remember Novell but that might be a little dated. AVI-NetworkGuy wrote: I would say it depends on what most people in your organization are using by way of platform (more Mac, or more Windows).

If you are mostly Mac (which I am assuming here since you had Open Directory), you might have some pain with moving to AD since there is no native management for Macs aside from the simple ability to join a Mac to an AD domain. If your plan is to switch to Windows on the desktop and server side, than you will only derive benefits from switching to AD. I would make sure that there is a solid business-driven decision to make this change. In other words, ask the question, 'How will moving to Active Directory help drive our business better than Open Directory does right now?'

He does make a good point, if you guys are a MAC shop it would not be that good of a switch. Anyconnect vpn for mac. Zak wrote: AVI-NetworkGuy wrote: I would say it depends on what most people in your organization are using by way of platform (more Mac, or more Windows). If you are mostly Mac (which I am assuming here since you had Open Directory), you might have some pain with moving to AD since there is no native management for Macs aside from the simple ability to join a Mac to an AD domain. If your plan is to switch to Windows on the desktop and server side, than you will only derive benefits from switching to AD. I would make sure that there is a solid business-driven decision to make this change. In other words, ask the question, 'How will moving to Active Directory help drive our business better than Open Directory does right now?' He does make a good point, if you guys are a MAC shop it would not be that good of a switch.

If you're a Mac shop you will only subject yourself to pain and torture by setting up Windows servers. Apple doesn't implement AD well, so you will have issues. And let's not even get started with the license costs. Don't forget to buy a CAL for everyone connecting to the Windows server, in addition to the cost of the server OS.

Frankly, you might be better off looking at a solution like Casper Suite from Jamf. It pretty much allows you to do with Macs what Windows admins can do with their machines.

Do NOT use active directory in a predominantly mac shop. It will save you zero time and create numerous endless headaches. Active Directory integration on Mac OS X has been in limbo since I've been implementing it starting in 2006. It is no better now than it was then. Get Apple Remote Desktop, which is $79 to manage unlimited clients.

Why Can't We Have Directory Services Like Open Directory (for Mac Download

This will allow you to run scripts, install software, run command line, all remotely and you can batch it all to as many computers as your heart desires. And you can remote into the computers to help.

I would also question whether you are leveraging OS X Server and OD correctly? What issues do you have with it? OS X Server is fairly feature rich and the management tools in OD are quite granular. Or you can spend thousands of dollars and hundreds of hours deploying an active directory environment and get to experience all of your worst nightmares come true. Tweets wrote: We have google so we can use that for chat.

We are familiar with Windows more than a linux. What problems are you having now with Apple OpenDirectory?

What are you hoping to accomplish with A/D or why do you want to move to Active Directory? From what you said it doesn't sound like ActiveDirectory would be the solution for you. There are a lot of licencing cost associated ith it (user/Device CALS etc) maybe if you really need to move away from apple for some reason this or something similar would work for you I would say if what you've got is working (and isn't EOLed) why change it? But if you do I would suggest an apple or.nix solution over a windows for your environment. You can use AD for ichat accounts and the like, but you aren't reducing servers as you would still need to keep your Mac server(s) in place to offer those services. You would just be spending more money to do what you already do.

The only thing switching to AD in a fully Mac shop is going to do is add licensing costs to your budget. GPOs aren't going to do a thing for a Mac unless you buy 3rd Party software. You will actually lose functionality in your LDAP settings by using AD because the schema doesn't support Mac schemas. If you wanted to set user or computer restrictions, you would have to extend the AD schema, which if you aren't comfortable with, could break AD and make you start it over again.just to use Workgroup Manager. OD offers SSO for all of it's services, which is why it makes extensive use of Kerberos, just like AD. OD also replicates between servers, just in a Master-Slave config rather than a Multi-Master config (which is how Active Directory is setup).

I'm actually looking at switching my entire district to OD and phase out AD as we don't take advantage of the extras like SharePoint or Exchange. Now, if you're switching to a Windows shop, then I would switch to AD.