apeman

what does lpstat -l show from terminal?

If you can't return the software and are forced to run it then this is the method you should use

Why have it sitting there doing nothing?? have it online and part of the network then make a redundant core with the pair.

Don't use the login hook, apple deprecated login hooks again ago You should use the launch agent PaperCut KB | Starting the Client on Mac OS with Launchd

If you go down the Windows route i wouldn't use Apache, i would use IIS on server 2012 or 2012 R2. You can probably have it up and running with about 5 lines of powershell. Never seen or heard of an issue running it under IIS, i use linux and apache myself but only because we run munki web admin on the same box and some frameworks weren't available for IIS.

Munki admin is a separate tool which is not written by the Munki developers thats why you can't find it when you download the munki package. I use the Munki Admin to manage my repo, it is a great tool. Be careful googling Munki Server as again this is another piece of software which isn't part of a standard install. All you need for Munki is a Webserver with 5 folders Pkgs, Pkgsinfo, catalogs, icons, manifests. I would aim to get this working first so you can browse from your client machine to munki.domainname.com/repo/pkgs etc once you can do this then start adding your software.

Munki 2 has been out since september 2014 Munki 2.2 came out last week which adds native profiles support. I wouldn't even bother trying to set it up on OSX Server, Apple has shown very little interest in there server side of things since they dropped the xserve. I would use Linux or even Windows as its only a web server your setting up.

This sounds a bit like an issue we had with aerohive and was fixed in the latest firmware that came out 3 weeks ago, are you running the latest?? @nikaso just for info Aerohive and Meraki hardware was identical in the older models but neither company will admit it.

My guess would be the flash plugin is causing the issue.

There is no Sysprep process but if you are using Deploystudio it does clean up a number of things like byhost preferences and local KDC for you. Remember Deploystudio is reverse engineering Apples OS so this is why it takes time for them to support the new releases. The current recommend way to deploy OS X is use an unbooted image using something like netinstall / AutoDMG or even use the OS thats on the Mac out of the box and use a software deployment tool to add the necessary software.

I am sorry but we have a lot of Little Dreams stuff and its a load of very expensive junk, most of it does look nice but isn't designed for heavy use by students and falls to bits very quickly.

We use this free tool Photos for Outlook, SharePoint and Lync it works very well but it only updates the jpeg or the thumbnail attributes at one time not both like the powershell will. You will only need the jpeg attribute if you are using something like apple mail.

i found 14 lots on the ground floor

The exchange management console uses iis even though its an mmc so i would say thats still where your problem lies, be careful running the repair commands they can actually make things worse.

Using too many GP's and WMI Filters can cause a massive performance impact, it is also a management overhead having lots of GP's to keep track of. Depending on how you name your computers could you maybe add some logic to your script?? i.e. If computer name contains room1 then map this printer else if computer name contains room2 then map this other printer etc This has the advantage of being one script applied at logon and in only one gp with no wmi so easier to manage.

The reason why your new polices don't apply is because you were only allowed one password policy until 2008 R2, if you did configure these settings they would only effect local account polices on workstation/servers If you have 2012 Domain controllers you can create the password polices from the Active Directory Admin Center so no need for the Specops tool. (probably works with windows 8 rsat tools but i haven't tried it)

Workgroup manager hasn't been supported since 10.8 but still sort of works as you have seen. From what i have read, only settings applied to computers or computer groups in workgroup manager get applied. You need to start looking into profiles for managing your mac's but its very limited as of 10.8 and i haven't tired 10.9 yet. As for your problems Are you sure its not mounting the share?? just because it isn't shown on the desktop doesn't mean it hasn't mounted. I believe apple have changed the way that dock and wallpaper get set so i doubt they can be managed with workgroup manager anymore. I don't use safari so i don't know if this works or not.

64 bit Windows and Office and no issues. We even got rid of JAVA too yay

You dont need two boot images for this, i am sure the x86 boot image can deploy x86 and x64 images. Its much simpler as you only need to maintain one boot image.

I am amazed people disable UAC, we haven't found a single application that causes an issue when we upgraded to windows 7 x64 and we have software from as far back as 1998. If you do find an application that does causes an issue you can usually work round it with Microsoft Application Compatibility Toolkit.

Yes its not instant failover but works very well and much better than 70/30 or 50/50 split scopes between server. You also get the added powershell commands

Please note i said a test setup in an hour. You would only need the RADIUS server (very easy to setup) as most people running 802.1x use PEAP and not EAP-TLS, PEAP only requires a server side certificate which can be created with self ssl or one of the many free certificate websites. I agree the problem is that the encryption key has been compromised but what is to stop this happening again?? just changing the key to WPA is not a fix as this key can still be compromised. I have not done this for a while so please correct me if i am wrong but the only way to deploy WEP/WPA keys is via a profile with a login script which is a bit of a pain and you run into the same problem if the profile gets compromised. WPA/WPA2 Enterprise is much more secure and allows settings to be pushed out very easily via group policy, it will only let devices or users you specify to connect to the network.

If i were you i wouldn't waste my time setting up another PSK wireless setup. It looks like your access points support 802.1x so i would go for WPA/WPA2 enterprise, it would take less than an hour to get a test setup going.

That is the date active directory uses as it start date for accounts etc. If you have enabled scavenging correctly i would say the value is miss leading and you just need to refresh your mmc console.

Scavenging isn't just as simple as turning it on at the root level, you have to enable it on each zone and only on ONE DNS server. I used to have a really good document that explained it really well but i cant find it. i would read as much information as you can find. This would be a good start Don't be afraid of DNS Scavenging. Just be patient. - Microsoft Enterprise Networking Team - Site Home - TechNet Blogs