eejit

Ah, got you - that makes sense. Thanks!

So you DO still get a normal Office 2013 download and a KMS key? Thanks.

Just a basic question guys - when you sign up to Office 365 do you still get a KMS key for Office? I know that you can log onto office.com with your account and install from there - it looks like app-v behind the scenes. That is no good for a school wide deployment of course, so I'm just wondering how that is supposed to be done? Thanks.

Awesome stuff @Brimstone - just registered for the free trial. Thanks!

Old thread but a few AirCatch questions on here. We are trialling it at the moment and it seems pretty good from what I can see is that there is no way to stop users from sending files to another users home folder. As @TopTech said you can add H:\homefolders as the location of your users and it then scans that folder and makes email accounts for all the usernames underneath. The end user then emails their doc to their username, such as fredsmith, but if you are fred smith then you can just as easily send the file to joebloggs. Before we commit to AirCatch are there any other similar products that we should evaluate. I've not had a chance to trial Foldr but does it have the same limitation as AirCatch and other users folders? Thanks.

Hi guys, I see that 4.5.2 is out this morning. Anyone in a position to test that with SIMS? I don't have a machine that definitely doesn't work with 4.5.1 or I'd give it a go myself.

Oh ok thanks. Interesting

Did you ever get a solution to this? I'm experiencing a similar problem to yours, but not quite as bad. If we rebuild a machine with the same name, then SCCM only sees the old machine, and "last activity" remains at the day we wiped it. If I delete the machine from SCCM and then do an "Active Directory System Discovery" then the new machine is found and the SCCM client and Endpoint get rolled out automatically as expected. There must be a way for SCCM to recognise a new build with the same name.

Have you deployed KB2775511? It's a must.

As others have mentioned there is a little error in the PowerShell code. $recycleBins = Get-ChildItem "$RECYCLE.BIN" -Recurse -Force foreach ($recycleBin in $recycleBins) { $recycleBin.Delete($true) } "$RECYCLE.BIN" should be '$RECYCLE.BIN' otherwise the folder gets interpreted as a variable. I've just used this and it flew through the data getting rid of GBs of recycled data almost instantly Get-ChildItem -Path '$Recycle.bin' -recurse -force |Remove-Item -recurse -force As usual, test yourselves first on some practice data. Cheers.

@Rozzer I'd also like to know how you set up this part if you have time Thanks!

I'm using Server 2012 R2 preview on my notebook and it is as solid as a rock so I'm sure 8.1 will be too. You will have to do a fresh install when the full version is released though

Certainly didn't like the 3D stuff - brought nothing to it, so that was a waste.

Gotta say that I loved it. On the way home we were debating whether it was the best of the three or not.

That's great news. The reboot after WSUS is vital all right Yeah, I generally work with VMs, so make a relatively small C: VHD of about 70GB and a D: drive of about 200GB for SQL, SCCM install, WSUS storage, MDT etc.

I've installed SCCM 2012 in almost 40 different sites and the link between SCCM & WSUS is the most usual thing to go wrong. In my experience the best thing is to remove the SUP component, then remove the WSUS role, reboot the server and start again. Let me just copy and paste some of my personal installation instructions and hopefully those will help even though you probably have done the same thing already. Installing WSUS: Add WSUS Role • Part of this requires the downloading of files, so you must have internet access when adding the role. • Save the data in D:\SCCM\Sources\WSUS. • Use existing database “” (You don't want WSUS to add another SQL installation when you've got a perfectly fine full SQL install set up for SCCM) • Create a Windows Server Update Services 3.0 SP2 Web site which will be port 8530. This ensures it won’t clash with any other port 80 websites that someone else may add later. When this wizard is finished close it, but do not run the post install configuration wizard as SCCM will configure WSUS later. • Install KB2720211 • Install KB2734608 Your WSUS should be left at version 3.2.7600.256. REBOOT YOUR SERVER NOW Configure Software Update Point • Start up the ConfigMgr console • Click on “Administration” >> “Overview” >> “Site Configuration” >> “Sites” • Right click on your server and choose “Add Site System Role” • Skip the first page. • Add proxy if required. • Chose “Software Update Point” • Select the 8530 and 8531 radio button. • “Allow intranet-only client connections” will suffice. • Synchronize from Microsoft Update. Do not create WSUS reporting events. • Create custom schedule of daily updates at 23:00 • Immediately expire a superseded software update. • Select “Critical Update”, “Definition Updates”, “Security Updates”, “Service Packs”, “Update Rollups”, “Updates” • DE-select all products for now. (Caution some Office and Windows will be selected and hidden by default - expand those sections) • Select “English” only and complete the wizard. • Go to “Software Library” >> “Software Updates” >> “All Software Updates”, right click “Synchronize Software Updates”. o Check the progress in: o “D:\Program Files\Microsoft Configuration Manager\Logs\WCM.log” o You will see “Starting WSUS category sync from upstream...” o Then “WSUS sync running” every minute for about 9 minutes o Once that is finished, re-sync updates to force their download. Check o “D:\Program Files\Microsoft Configuration Manager\Logs\wsyncmgr.log” o It will take about 5 minutes and at the end you will see something like: o “Done synchronizing SMS with WSUS Server Server.domain.pri” Tip: WSUS doesn’t know which new classifications exist so doing the first online sync before choosing any products is the correct procedure. This will also update all the WSUS product categories and you should see “sync: WSUS synchronizing categories” in the log. At this point go back to the Software Update Point and select the products you want to protect. Then synchronize the updates again. Hope that helps.

The biggest problem I think is the seemingly never-ending day due to remote access. You help someone once out of hours as a favour and it's surprising how quickly out of hours fixes become expected.

I'd love to know the UK figure.

In my experience having WSUS set up "normally" can cause problems with SCCM. As a matter of interest, why would you want to do this? The updates management in 2012 is far superior to using WSUS alone. With SCCM 2007 there was a lot of hand-holding for sure, but now you really can "set and forget"

I use that Matt, and it is great, but how do you actually log off Server 2012? :S When you can't use the Windows key in a non-full-desktop remote session (that I know of, pressing Win-key opens the local copy) you miss out a lot of the possible options. I know I generally have to open cmd and type "shutdown -l" Am I missing something?

The selective sync is what sets them apart. Great to sync different folders to different servers\PCs.

Are any of you in a position to give a comparison between this and Windows Media Center? WMC is becoming a PITA due to problems getting accurate EPG information.

lol - this has the makings of a GREAT thread! *gets popcorn*

Thanks for posting this - had the exact same issues accessing OWA internally.

In my experience this usually ends up being a DNS problem. Netsupport's tech department are great though - always know their stuff very well.