Search the Community

I'm a bit of a Mac newbie as I'm more used to working in a Windows environment. However, there's a couple of things I'm trying to achieve. To explain the setup we have a Mac server (running on 10.9.5, Server version 3.1.2) which is integrated into Active Directory via our Windows 2008 domain controller. Also all the mac client machines are set up with the Golden Triangle too. Users can log on to any of the macs with their AD credentials with no issue at all. The problems lies in the home directory. I am able to allow users to access their Windows home directory, BUT this isn't the default Home location. That defaults to a local folder on the Mac client. This means users are saving work to this local folder, then going to another mac and unable to access these files. What I would like to do it one of two things - neither of which I seem to be able to implement. 1) Set the default Home location on the macs to be the same as the Windows home directory - and therefore not have a local home folder on the Mac. In effect having a single shared Home folder on both Windows and Mac networks. I gather this may not be ideal though at the Macs generate a large volume of data in the Windows home directory before even the first user file is saved. I would still like to explore this however, especially if what I have been led to believe isn't too much of an issue. 2) Set the default Home location to a folder separate NAS share for logging onto the Macs, and also allow users to access their Windows home location as an additional share. That way both Mac and Windows folders should follow them round as they move from Mac to Mac. My problem with implementing either of these options is that I don't seem to be able to change the "Home Folder" setting for AD accounts in either the Server Application (the option to change the folder is greyed out when selecting an AD account, however OD accounts - which we don't use - works fine) or via Workgroup Manager (which gives an Unexpected Error - 14140). As we have a large number of users, and a fair few Macs I would need to be able to implement a solution centrally. Any suggestions or pointers would be much appreciated. Cheers, LSDWho

Hi, Just to give a bit of background, I've recently completed the Apple desktop and server training courses to get the ACTC certification. This is because we've recently had an influx of Macs on our network here and nobody else wants to touch them! Anyway, I am still relatively new to the world of Macs myself and realise I still have a lot to learn when it comes to putting theory into practice, that being the case, I've bee having trouble getting ARD to work properly, primarily with regard to deploying software updates. Some background: we have 3 Xserves with Mac OSX Server 10.6.8. One is the main server and the other two are replicas. We use Active Directory to manage user accounts, with OD on the main Mac server administering preferences and services for the Mac clients. We now have around 60 Mac client machines on our network, all of which currently run Snow Leopard as well. These Macs are all bound to OD and AD. However, for day-to-day administration, we have a Mac that sits in the main IT office and is on the same VLAN as the Macs (which are on a segregated portion of the network at this institution), and with the admin Mac, I can remotely VNC to the Mac servers as required. Over the summer, we had a server rebuild and prior to that, ARD was used from the main Mac server to manage the client Macs, but since the original server build was set up by an external consultant who did not document properly, we couldn't find the original license information and ARD was left off the server post-rebild. As an alternative, a later version was deployed to the admin Mac (which is running Lion). Now here's my problem. I can run ARD fine on the admin Mac, it detects all the Macs on the network (which I have grouped etc) and I can control their screens, but I cannot do any remote management with it whatsoever. For instance, when I try to deploy (much needed) software updates through ARD, it returns the following: "Error: The operation couldn’t be completed. (NSURLErrorDomain error -1102.)" The only way I can get updates to work is by logging directly to a client Mac and running it manually. When I try to do this through ARD, I get that error. We have the software update service on the Mac server and a repository for storing them, and the clients and servers can update fine, but just not through ARD on this admin Mac. I suspect that since the admin might be having trouble accessing the software update repository on the server, but I'm really not sure. I've googled this issue quite a bit, but there seems to be very little information on this one error (typical) and the information I did find wasn't really relevant to my situation. I thought that maybe the Mac had to be directly bound to OD to be able to "see" the software update repository, but this hasn't worked either. This is driving me up the wall; I just cannot understand what the problem is here and it's especially frustrating that I can find no information on this error message, even on Apple's own website. I would be grateful if anyone here could assist. As someone new to all things Mac, this one has me well and truly stumped.

On one of our iMacs I'm getting an error when trying to logon to Workgroup Manager - an error of type- 14473 occurred, and then I can't log on. On the same machine I've got an error on my virtual machine (Windows 7) which I'm trying to install a printer by Desktop Authority, and also run sims on. The error is when mapping the S: drive at logon - shows 'unknown error 67 67' and also fails to update the printer assigned, with an error downloading the driver (Using Desktop Authority to map those on the Windows Network) I've trawled the Mac forums, not had any joy... If you could brighten up my dreary Wednesday by shedding a little light on this I'd be very grateful! Thanks in advance.

So I've recently got a network up and running for our macs. They are using a Windows Server 2008. I have an issue with some of the student accounts - they keep getting a message saying "OSX Need to Repair Library to Launch Applications". I'm given 2 options, cancel or repair. I have to put in admin username and pass to be able to click repair. No matter which option I choose, the message comes back a few seconds later. I have found that it is only happening with certain users, not the mac itself. I've ran disk utility to check permissions, everything is fine. Any idea what is causing this?