Sam_Brown

K. I don't mean to come across as being overly negative about it! Especially when I've not had much hands on experience myself. I'll shut up now and let someone else talk!

If it works...

^^^ Not sure if on purpose or not but you've missed off half of TheCrust's last paragraph which makes it looks like his comment applies to LAs! Anyway my query would be how many people find S3 an improvement over S2. I always believed the general consensus was that it wasn't and the benefits were outweighed by the problems. Obviously they'll be the odd anecdotal evidence to the contrary that it works great but from my experience the overwhelming opinion is it's not worth the hassle. I'm willing to admit I may be well off and I haven't used it much myself. It's just all the schools I've had friends work at have had issues with it in some form of another over the years.

One primary school I know recently had a new SIMS Server Installed and Capita insisted on sticking SOLUS 3 on it. Had no end of issues during the first few weeks with it not working with CC4 \ Existing Installations of SIMS. In the end they have a test machine which is the only one listed in SOLUS 3. This one gets all the updates and upgrades and then they just copy the whole SIMS folder to any other computer that needs it. Apparently it's a hell of a lot easier scripting deleting and copying over the entire SIMS.NET folder than it is getting SOLUS to work consistently on the entire network... Not sure how many people would agree with this practice but aparently they've had no issues since doing it that way and the amount of time spent on upgrades not working is near enough zero now!

Yeah I've been advised similar over the past year or so! What was the reasoning behind moving to SOLUS 3 over say releasing SIMS Upgrades in an MSI format?

Heard so many bad things about it over the years and dreading the day we need to (are forced) to move to it. Is it pretty much a certainty that we're going to be forced to use it within the next 12 months or so because I'm really not looking forward to that day!

Interesting... I've rebuilt some computers remotely and it works fine and some don't. Can't quite figure out why. Frustrating as the Deployment Reports states everything is a-ok!

Morning, We've got SCCM 2012 installed and running. Working fairly well as we've built a good 500 computers with it over the Summer and managed to remotely deploy Applications as well! What we're looking into doing now is Rebuilding IT Rooms remotely. I deployed out a TS and set it to "REQUIRED" and "SCCM CLIENTS". I left it running over night. I looked in the monitoring area of SCCM this morning and it has a 100% compliance rate and everything was green! Happy days I thought until I went into the room and noticed that none of the machines had actually been rebuilt at all! Any ideas on where I can look to begin problem solving this one?!?!?!

Is it not easier to allow end users to update SIMS on their own?

What does an nslookup give you? And have you checked your internal DNS servers to make sure there's an entry for it in there? How about connecting via the ip address rather than the name?

@andy - Not something we've had to do before but certainly worth a test. You could try importing one of the old .wim files into SCCM under the "OPERATING SYSTEM IMAGES" part and using it in a task sequence. Really have no idea if it will work or not though.

When creating a TS based off a Windows image captured from a B&C do you need to add installing the Config Client in the TS as well? Or is the fact it's captured already in the image from the B&C process enough? This may be where I was going wrong. Deploying it in the original B&C image and then again in the TS based on that captured B&C image... I hope that makes sense!

I wish I'd have known this at the time! Probably why my client kept on screwing up! Would build a computer based on a BnC image and the client would never install properly! You think this is related to what you're talking about?

That might mean you've made the TS available to "ONLY CONFIGURATION MANAGER CLIENTS" when you deployed the TS. You could try redeploying it and altering where it's made available to. You've got a few things to try really. But the first thing is making sure it's set to a deployment type where PXE is allowed. As for Build and Capture. There was a topic on here a while back about the merits of it. Personally I never saw the benefits of Deploy and Capture over building a machine from scratch using the default INSTALL.WIM although I know there are people who disagree with me on that one! I did try it although it though although found it created a few issues I never had time to fix so resorted to building from scratch which has always worked so far!

That's good news. Basically means it's talking to the SCCM server but the SCCM server doesn't have anything deployed to the collection the PC \ Laptop you're booting from is in. A few steps you may have missed... * Create Task Sequence - This is where you'll set what O\S to install, what drivers to use, what Applications to install etc etc. * Distribute Content - You'll have to make all the content the TS needs to run available on a Distribution Point. This is things like the O\S image, Boot Image, Drivers etc. * Deploy the TS to a Collection - Basically make this Task Sequence available to the computers in a specific collection. If it's a new computer not in a collection already then deploying it to the UNKNOWN COMPUTERS collection is probably the way you want to go although please please bare in mind the below... IMPORTANT!!! - Make sure when deploying your TS to set it to "AVAILABLE" and "ONLY MEDIA AND PXE". The last thing you want is to accidentally start to re-image everything on your network with the Config Manager Client on it! Setting it to REQUIRED and pushing it to a large collection is a sure fire way to accidentally re-image everything on your network!

You'll download the .com file and this is basically nothing more than a tiny program to enable you to then download the Windows PE Boot Image (this is what handles all the tools to image your computer). Providing you're fully 64-bit compatible you should only need one .com file and one Boot Image. Funnily enough my option 67 is set to... smsboot\x64\wdsnbp.com Once you get that far that Windows PE has been downloaded then you get to chose what Task Sequence you want to run etc. This is when you get to chose what images you want to use such as Windows 7 or Windows 8. Blue screen could be you're trying to run the wrong boot image such as trying to run x64 on a x86 system or that it doesn't have the right network drivers in it. Could also be the hard disk. Try setting the bios HDD settings to Legacy. This has fixed some of our issues before.

Morning All, Looking to get offline folders working on Windows 7. We believe we've set everything up correctly although seem to be having some issues.. Home areas are set in the format... \\SERVER\HOMEAREASHARE$\USERNAME HOMEAREASHARE$ has EVERYONE with FULL CONTROL on the Share itself and DOMAIN ADMINS \ ADMINISTRATORS \ SYSTEM as FULL CONTROL on the SHARE FOLDER SECURITY with ALL USERS having TRANSVERSE FOLDER \ LIST FOLDER \ READ ATTRIB \ READ EXTENDED ATTRIB on the SHARE FOLDER SECURITY. In terms of the USERNAME folder the individual users have FULL CONTROL over their own folders with ADMINISTRATOR also having FULL CONTROL. On a end user laptop Setting the H: to Offline and doing a manual Sync works fine. However it won't automatically show up under Sync Partnership Details. On the flip side NETLOGON seems to be Syncing automatically. In Group Policy we have assigned the H:\ drive as an Administravely Assigned Offline File however it's not automatically showing up :/ Any ideas?

Sounds like a permissions issue. Check the Share and NTFS permissions are set up ok on the RemoteInstall share, relevant child folders and .wim image on the WDS Server?

In "Active Directory Users and Computers" if you look under System > System Management then you should find an entry called SMS-Site-XXX where XXX is the site code. You'll probably need "advanced features" ticked under the "view" menu to find this. [edit - FN-GM's way is probably easier]

Personally I wouldn't use the same code. I'm sure it's perfectly possible to reuse codes after going through AD etc removing anything referencing the old set up but at the back of my head they'd always be that little niggling doubt that I'd probably forgotten something. On top of that I'd always be concerned that every time there was an error or strange behaviour I couldn't explain that I'd be drawn to the fact it might be because I'd missed something... but then again I normally urge on the side of caution so it might just be me.

The school is looking for a motivated person with excellent communication and organisational skills to provide on site ICT support and network management to nearby primary schools. The successful candidate will have a good working knowledge of Windows XP/7 and Server 2003/2008, VLEs and managing Webpages. Working experience with RMCC3/CC4 and tablets desirable but not essential. The school is committed to safeguarding and promoting welfare of children and young people and expects all staff and volunteers to share in this commitment. Salary: £15,053 - £16,777 Full details can be found below: Vacancies | The Duston School Any questions please let me know and I'll try and answer them.

Not used FMS for years but does it still insist on that f***ing stupid PDOXUSRS.net file being on the route of the C:\ drive? We used to have issues with this that sounds similar to the ones you're having that could be resolved by moving the file from the route of C:\ to a folder and configuring FMS to look for the file somewhere else.

It appears to be working now. I created a specific TS just for the problematic Dell machines which only included the drivers from the CAB I got from the Dell Website. Using the Original TS it would use drivers from 2013... I noticed that when removing the USB Controller Devices from Device Manager and restarting that they came back and started working and instead were picking up a 2008 version of the same driver. Strange... it wasn't a case of using a driver too old... it was a case of using one that was too new!

Completely clean TS from scratch. Using the base install.wim from Windows 7 SP1 CD. Have already got the Dell 760 Cab however haven't specified to only use this when building the machine. Will create a new TS and limit the drivers it can use to the ones from the CAB and see if that works. Thanks for the idea.

Afternoon All, I seem to be spending half my days asking questions on here so apologies in advance! Imaging some Dell Optiplex 760s. Everything goes fine and all drivers seem to install however USB Keyboard and Mouse don't want to work! RDP onto the machine and check device manage and all drivers are indeed present however the USB Controller Drivers are complaining about being unsigned (goes into some detail about being changed since they were installed). To rectify the issue I have to remove the controllers from device manager and restart and they show up right as rain (albeit it takes maybe 45 seconds for the PC to find the keyboard and mouse at the next boot). KB and M works fine in Windows PE and BIOS but as soon as it boots into Windows 7 that's when the issues occur. Is this something someone has encountered before at all? Manually removing the device isn't a particularly massive deal however it brings out the OCD in me where I want everything to work without needing any sort of manual work on rebuilds!!!! Any ideas?