TheScarfedOne

That'll be my cue to come in and say 'ello then Witch??!! Indeed - there is something in the pipeline. More info to follow soon... On a more general meet, speak to the SWGFL or your LA IT Support Team. From experience, they will always help out with arranging meets and agendas etc. SWGFL and SCOMIS have been good at this for those in the Plymouth - Taunton area.

I have just completed a full rollout of Thin PC to connect to my RDS farm. Wyse Think clients will be connecting to that soon too. Stuff on my Edugeek blog about the Thin PC bit, the Wyse stuff will follow when they arrive next week

Heres a script to add to the deployment sequence which will do just that. Put it in as a program (with package) after the Configure Disks section... PromptForPCName.7z

Im with the last posts - if you have a problem with the way the site is working, please message the admins. The feature is there for that reason! Failing that, drop one of the Mods a PM. If you get Negative rep'd, report the post and we will look into it. This kind of discussion really shouldnt be going on in public, doesnt help with the professional image of EG.

swap to using the new version fep - which has native support for it built in as fep is built on top of sccm. How to Deploy the FEP 2010 Client Via OSD and Test Deployment - TechNet Articles - Home - TechNet Wiki

Lots of bits on my edugeek blog about deploying 7 with sccm. other good places include http://www.windows-noob.com and technet

Belated happy birthday! :-)

OK - so some of you now know I moved on from my last School - where I was very vocal with Sharepoint and later SCCM. Well, now at my new Academy - we are going to get down and dirt with virtualization as well. You may have seen my last post about SCCM and AppV; and also Windows Thin PC - which is part of the story, and also our testing and QA process. Whats going in then? Well, to sort out the underpowering on the Server side - incoming 2 x Dell R710s with 300gb Raid and 128GB RAM; and an MD3200i with 8 x 2TB SAS yet to decide on the arrangement on there - but there will be separate VHD storage, SQL Stream and User Data storage. This will be used to virtualize the Server Platform. Exchange will go onto it (splitting DB from CAS - currently single server) and being upgraded to 2010 SP1 at the same time from 2007. SCCM will go over too. Currely single server from our testing and QA - but its a simple migrate; it will also become a two server platform. SQL will be clustered - hosting SCCM, Forefront, SIMS, Eclipse and TMG databases. It will also later hold Sharepoint databases too - but that one will be setup towards the end of the summer - again a two server structure. DFS for User Data access will move off the two physical DCs, leaving them to do just DC work. There will also be a RDS Farm for the Thin Client system - which I will come back too. Also moving onto the virtual platform will be the Runtime software share and your old style Staff/Student shares. These will go DFS too, with replication. Thin Client then... two different ways being used. The Windows THin PC section - reusing some older equipment namely some Celeron 2.6 RM Ones, and IBM SFF ThinkStation Celeron 2.9s. Runs nicely. Then, for our Admin section - Wyse T50s, some dual screened. The T50s come with the VESA mount kits and will be attached to the back of the TFTs. On the dual screening - heres how: I didnt know that! Anyway, wish me luck! Oh, and the whole platform for the site is moving to Windows 7 too. System Centre will be doing that upgrade for me though, easy peasy! And app installs are a dream, as most of my apps are actually AppV apps. Helps as my RDS servers then wont actually have the apps installed on them either! Questions and comments always welcome

I would suggest posting this as a question in the Windows or Windows Server Forum... Im not a CC3 user, but as you say that you arent using CC anymore - I would expect that removing any CC related files from you server should have no impact. Stuart

hmmm, definately not needed to do that on mine.

Not again! Easy on the milk, and no sugar for me please :-p

I sit firmly in the MDT, System Centre Essentials, SCCM camp. As said, it does the driver injection stuff - and you can cover off the app deployment too. If you do go system centre - you have the advantage of heading off with Forefront for your AV....

Yep - plus one for QRES here. Use it as part of my SCCM task sequence at the end of the build and on logon/off as well. Has a commandline interface for scripting

Yep - i would put this as the last task in the sequence after installing any software etc, followed by a reboot.

Hmmm, having just finished testing this and now building the final system - I would recommend using the Server 08 R2 rdp. You need to licence rds, but it is properly designed for the process you want to do. If you create your rdp file, then yes it is an option - usb and pnp devices.

@edugeekdan... this one is set in group policy on the server. Create and link a GP for the OU/Machine. The setting is in Computer Configuration > Policies > Windows Settings > Security Options > Interactive Logon: Do not display last username

This sounds very odd to me. AFAIK, all SWGFL schools have access to the ESI system - where you can log your own calls for support or change requests. Before that SWGFL Support did the same thing. Please do follow this up with Richard - they do genuinely try to help. If you cant give the call ref, give him your establishment code - he, or you (if you go into ESI) can then look up the reference and get to the bottom of it.

Ive seen this a few times, it usually happens because the Collection membership hasnt yet been picked up. Change to discovery cycle on your collections on the server to be more regular. Ive set mine to 1hour - as im still testing and keep changing things! If you right click collections in SCCM console, then update membership, ok the message and wait a few mins - the client should get the rest of the options after a reboot. If you dont want to reboot, run the machine policy retrieval. Think of it like a GPUPDATE. That should fix it for you.

There is one on my blog. Posting from mobile so cant include links :-S #fail!

The advantage of having them on domain is that they are GP'd and patched and managed as part of the main system. You can push all RDP Client settings in GP. The user in our case is a restricted network user. Plus... we use SCCM to build, manage and patch across the site. WTPC builds/deploys in the same way as 7. Ive since found that I could have changed the Shell in GP rather than the first build vbs which tattoos some parts of the registry.

Mind you - I did want to make sure I dont have to do this again any time soon. At mo, there is not enough kit to sustain the system its running

Thats good pricing! Might have to check that out myself (the company that is)... I dont think your LA with like the distance :-p

Ive gone even further than that! Dell R710 - 2x Quad, 146GB Ram, 2x 300GB 15k for OS, and Dell MD3200i SAN with 8 x 2TB drives in separate arrays for VHDS, SQL Stream and Data

Right, an update. It works a treat, and ive updated my blog with how ive got it set up. On the logon timeout issue - will have a go at that and let you know. What Ive done is set the WTPC to autologon, and changed the shell to be RDP, and set it to run in kiosk mode using a third party free app. This makes the process unkillable (and make sure you gpo disable task manager)... all that happens is when the session is not logged in the client will keep cycling. May not be too pretty, but it works fine.

Shameless plug here (Im a Systems Manager before anyone hits Report Post :-p)... doing this at the moment with Windows Thin PC, which is Windows 7 cut down to use as a Thin client. Posts on my blog about setting it up with RDP.