TheScarfedOne

That sound like a nifty addition

I thought I should chip in on the System Centre side of things... v4.6 integrates nicely with SCCM, as does v5 but Ive yet to have it confirmed whether SCCM2007 will support v5 packages or not. 2012 I believe will support both. I use it to virtualise CS4 entirely (so I can co-exist CS4 and CS5) and also a load of other apps. Its a genius piece of kit... there is some up coming blog stuff I am writing with MSFT on this which will appear over on the MS Schools Blogs pages, and then a day or so after on my blog too.

Welcome to Part 5 of my now EPIC System Centre Configuration Manager (SCCM) series! Heres the 2nd of your "two for you money" weekend deal :-p. So - this time round we are going introduce a new dark art - Task Sequences. These are the power of SCCM; and will actually get your deployment off the ground. After anything specific Ive not covered, or that you think Ive missed, please comment or send me a PM. Alternatively, you can find me on Twitter @TheScarfedOne. Introduction to a dark art sequences are the power of SCCM… they are what actually controls what happens on your machines. There isnt much you cant do with them… they are incredibly powerful. Task Sequences can be linked to Operating Systems, Drivers, Applications, Scripts, Software Updates – well, most things like I said. To start with, we need to create a Task Sequence (TS) to install Windows 7 in unattended mode to a target machine; and then to capture that install (including SysPrepping it – remember as you did in XP) and save it on the Server for us to use later. Thankfully – SCCM makes this easy for us, as one of the options on the New TS menu is “New Build and Capture”… nice work guys! See... not such a dark art maybe! Creating your first TS So, lets get started (I have attached a sample TS for Build and Capture which you can import if you wish – but its good to try doing it yourself once to get a feel for the TS environment… you will be doing a lot in here once you get running with SCCM!)… Now… I don’t like where TS has been put in SCCMs interface; as you can do more than OS’s with them. But, hey ho, it is under the Operating System Deployment node. So, right click and choose New Task Sequence from the options shown. As I said, the developers did a great job here (apart from where in the interface it appears… grumble grumble)… so choose the obvious choice - Build and capture a reference operating system image. Give the it a sensible name such as Windows 7 - BUILD and CAPTURE, followed by clicking on browse to choose your boot.wim file (the ones we created right back in the first posts in this series), choose the 32 bit one. Next up - SCCM needs to know what operating system we want to install – so it can do all its fancy stuff in the background. Now, assuming that you have followed my previous blogs on this series – you should see your Windows 7 DVD option in the browse and drop downs. If you don’t – you have probably fallen foul of the main mistake people make in SCCM. That is that you have built a Package (and that Package could be OS, Application, Drivers…) but not added distribution points! This happens a lot, but remember – every time you make a package – you MUST distribute it before it is available. With Applications and Drivers, it will tend to be a “Fails to install” or “Fails to run” with error 8004005. For the Build and Capture, you don’t need to worry about the Product Key. It doesn’t need it. When doing your actual deploy, then you should use your appropriate one. Again, on the password option – for your “Master image” you don’t need to do this – as you will actually set this on the Task Sequence you use to send out your captured image to machines. Next up is setting the network configuration – where you should choose Join Workgroup. This is obvious really, keeping it off the domain will keep it clean. We also need to specify the Configuration Manager Client installation package we created earlier from the predefined packages, select it by clicking on browse and selecting the package. SCCM has the power to install OS and other updates (supported by WSUS) as part of the build. Again, as this is a Master image, you will likely have already slipstreamed in SP1, or got the SP1 media. I would recommend that you choose 'don't install' any software updates. As part of your actual deployment of the captured image, you might want this enabled – and choose the set you have ready. That is outside the scope here – but as the feature appears here – it made sense to cover it off. Install software with your Master or after your Master Ive split this section out from the main article – as there are two schools of thought on this. Some people prefer some of their applications to be included as part of their master image. Others think they should all go on after. On as part of the image will slightly decrease the install time – depending how many apps you include, but on the flip side – your image will be bigger. This may take longer to transfer to your clients at build time, and maintenance of your image (see updating applications) be a bit more testy! Doing it after image time, as part of your deployment gives you more choice and control over where and when apps go out. You can also strip them back off machines reasonably easily. The choice is yours! Anyway – where is how you would do it. On the “Install Software” screen - click on the yellow star and select a software package you have created. The screenshots here show a Firefox package. Software packages must contain a program (the program tells the package what to do) – and each may contain more than one program. You select the one you want. Finishing off your Build and Caputure after our detour Remember I mentioned SysPrep earlier. Well, if you were deploying XP - then you would need to select the package here. However, all OSs since Vista have the sysprep built in so no need! Next up, well nearly done, is giving some extra description information to our Image. This will help you identify it later when you are building up a catlogue of images. Finally, we need to give SCCM all the details about where on the network we will store the image once it's built it. Remember in the last article we were creating a load of shares and folders? Well, we will be using one of those so \\SERVER\SCCM-IMAGES\SCCM-Win7-x86-DATE.wim should do nicely. Oh, you also need to give SCCM an account to logon to this share with. You will get the usual summary screen next – and that’s it! Your first foray into the world of Task Sequences! Want to take a deeper dive and see whats going on under the surface? Why not… Task Sequences… a deeper dive When the Task Sequence is complete, you can right click on it and and choose Edit. By default, SCCM comes with 28 tasks that can be added to the task sequences. This includes everything from partitioning, joining the domain, formatting and setting up disks in addition; and - the integration with MDT (Microsoft Deployment Toolkit) means that MDT adds an additional 9 tasks. This is where you could define where to add SERVER ROLES AND FEATURES for Windows Server 2008. Options can be added from the Add dropdown, and edited in the window on the right. At the moment, this TS does nothing – until we assign it to a Collection in SCCM. And that’s whats coming up in Part 6, and Part 7 will show you the end results. That should be up shortly (Im writing them both at the moment!). Enjoy!

Welcome to Part 4c of my System Centre Configuration Manager (SCCM) series! Yes.... this one has been a while coming - so Im going to give you two for you money today! So - this time round we are going to finish off the building your first Windows 7 image. After anything specific Ive not covered, or that you think Ive missed, please comment or send me a PM. Alternatively, you can find me on Twitter @TheScarfedOne. Drivers - aka the HELL! One of the issues you'll probably face sooner or later with deploying OS's is not being able to access network or storage resources due to missing drivers within boot.wim - or once the OS is building and installing (well trying to) applications as part of the Task Sequences. To deal with this - we need to give SCCM a pile of drivers, but before doing so create a share on your network and copy some into it. Quick health warning here - PERMISSIONS! Make sure that the permissions for that share allow READ/Write access for your SCCM account (and preferably SYSTEM as well). In addition make sure that the SYSTEM account has NTFS permissions that give it full access. A general rule of thumb here - go with a simple naming structure. So... I generally advise the following: DATA DRIVE on SERVER :: SCCM-IMAGES (for SCCM Build and Capture to drop its image into) :: SCCM-SOURCES (for SCCM to read its information out of - contains subfolders of APPLICATIONS and DRIVERS) :: SCCM-PACKAGES (for SCCM to write and maintain its own package structure - contains subfolders of DRIVERS and APPV [NB APPV uses its own package maintenance structure in SCCM. Normal packages don't, they use a SMSPKG*$ where * is the drive letter]) As with everything in SCCM, drivers must be added to packages and deployed to distribution points before computers can use them. Adding Drivers - and best practice What I prefer to do with drivers is maintain a single massive repository. Some people prefer to have separate Driver Sets for their machines. This is fine, but what you might find is that you get a "Driver already exists" on importing. So, in the DRIVERS folder in SCCM-SOURCES - I create an X86 and X64 folder. Then , in there go with the common hardware types - GFX, AUDIO, CHIPSET, LAN, WIFI, etc. Some who are familiar with drivers from the RIS days (shudder) will remember a great project called DriverPacks. Well, its still running - and has pre-built driver sets by type, which you can then import into SCCM. One issue - due to the size, they are now distributed as torrents - which I doubt you can download in School. Once you have got them (a series of 7Zip files ), extract into your folders as above. Then you are good to go. You can find out more about the DriverPacks project at http://www.driverpacks.net So - the import process... In SCCM ConfigMgr, find the Driver node under Operating System Deployment section. Right click and create folder. What we are going to do is create a "virtual" folder structure in the console to mirror the layout of our share. It will make life easier later. So - the first folder is x86, and on the same level x64. Then in each of those - LAN, CHIPSET etc...! Right click the appropriate folder (we are doing LAN drivers here) and choose import. When the wizard appears paste in the path to your network share containing the drivers, which should be something like \\SERVER\SCCM-SOURCES\Drivers\x86\LAN (I'm using LAN here for a reason - which will become clear in a moment....) SCCM will go away and look at all the .inf driver files in the location. After a while it will list the driver(s) it found, and you can then click on categories to place them into a category. Categories are useful to help deal with limiting what drivers are available to what machines (i.e. x86/x64 and others, where you may in future add specifics for some laptops for example). Click on Catagories to get to the options screen. As this is our first one, its bank. Just enter a new one (something sensible like Windows 7 - x86 - LAN), and click Add, and then OK. You will see it appear in the "Assign categories for filtering..." field. Click Next, and then Next again on the Packages screen. We will be coming back to this one, so you don't need to click the "New packages" option - but you could do if you wanted to do it from here. It will trigger the same wizard we will be coming to soon. Next you have the option to add these drivers to our boot.wim files, as we are adding Network drivers then you should select the X86 and X64bit SCCM boot.wim files listed, make sure to also place a checkmark in Update distribution points when finished. You will be clicking Next twice, and then sitting back and waiting for a while. Seriously - this can take a while too, Ive thrown a set of 50 odd drivers at it once, it took about 45 mins. Bear in mind, with LAN drivers, it is also updating your boot.wim too. You only need to do this with LAN drivers. Some people do it with GFX as well, to make their boot screens look pretty, but thats up to you. Remember, the more drivers you put in - the bigger your initial wim - and the longer the first SCCM boot. Next up, dealing with driver packages. Drivers have to be in packages to be assigned to machines. So far - all we have done it inject them into our boot file. You can think of this like adding a software app, without all of the setup files... it isn't going to work...! Adding driver packages As you will have got the idea of by now - most things in SCCM are where you'd expect them. We need the Driver Packages node in SCCM ConfigMgr and right-click, choose New Driver Package. Remember earlier on we created that share SCCM-PACKAGES? Well, we need that now too. Have that open in one window - as annoyingly - you can't create a driver package in a folder that doesn't exist - and it will moan at you else. I went through in advance creating SCCM-PACKAGES\Drivers\x86\LAN; AUDIO; WIFI; GFX; CHIPSET... just to be ready. In the wizard that appears fill in the details and point it to your share (its important to make sure that this share is separate from the drivers share - SCCM stores a load of extra information with the packaged drivers). Then, simply click ok to create the package, we now have an empty driver package. Back in your SCCM tree, you then need to go to the Driver node again. Down to the LAN folder we made in x86 - and we should see all the LAN drivers we had imported earlier. If you can't see them - press F5. We need to select all of them (this is where when doing other Packages later - you could use the Create package and Add to package all as part of the import process; alternatively, pre make all of the packages then do the import and add at that point as the import wizard will show you the packages that exist). Once you have selected them all ("Ctrl - A"should do the trick) - in the Actions Menu on the right - choose Add or Remove Drivers from Package. You could right click, but you run the risk of loosing your selection! A bit of clicking next, and thats that done. You can check it by going to the Package under the Packages node - again, you may need to F5 for a refresh. Now that we have our drivers imported into our drivers package, we need to Create a distribution point, so lets right-click on Distribution points and choose new distribution points. We only want standard "Server" ones again here - so don't choose the PXE one. So - all you have to do is repeat that process for all your drivers and SCCM should be able to deploy onto any hardware (x86 or x64 - assuming you do both sets) - with all drivers. Now we have done that - time to actually make the master image in SCCM by doing that Build and Capture - the title of this section of the series. For that, we learn about a new concept called Task Sequences. That will be next... so stay tuned!!!

Check your expiry and start time on the TS's. And also whether or not the ReRun behaviour is set correctly

One from System Centre 101 - double check that you distribute packages to DPs... usual error is the 8005 or 8004 for that one

RIGHT..... some bug testing on Scenario 1.... System default for max days in advance is 18 days. Set ABR to increments of 1 week to find the point where the error is thrown. Thrown at week 8 from today. Week 8 coincides with a holiday (June HT). So... it looks like it might be connected to when the system sees ABR overlapping into a holiday? But still doesn't answer why Overall admin rights given through HAP Config result in all permissions except no days in advance... hmmmm And I saw your "Week 9" post too late... but hopefully the above helps outline whats happening... ABR = 9 also still generates the error. So it looks like it is to do with how ABR sees holidays as you suspected.

And Scenario 2, the user is put in an AD group - this group is selected in HAP Config: User gets the "Control Panel" option shown, can override bookings, and book on behalf of others - but the date selector will not allow going beyond the system default still.

Ok... going to be a few separate posts here... Scenario 1: User has ABR's set - below 10 and over 10 days in advance (and is not a Booking Admin) results in the following Server Error in '/HAP7' Application. -------------------------------------------------------------------------------- The added or subtracted value results in an un-representable DateTime. Parameter name: value Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.ArgumentOutOfRangeException: The added or subtracted value results in an un-representable DateTime. Parameter name: value Source Error: Line 86: Line 87: var curdate, curres, curles; Line 88: var user = { <%=JSUser %> }; Line 89: var resources = <%=JSResources %>; Line 90: var availbookings = [ 0, 0 ]; Source File: d:\Program Files\HAP7\BookingSystem\Default.aspx Line: 88 [ArgumentOutOfRangeException: The added or subtracted value results in an un-representable DateTime. Parameter name: value] System.DateTime.AddTicks(Int64 value) +9624435 System.DateTime.Add(Double value, Int32 scale) +136 HAP.Web.BookingSystem._new.get_JSUser() in H:\Documents\Visual Studio 2010\Projects\CHS Extranet\HAP.Web\BookingSystem\Default.aspx.cs:174 ASP.bookingsystem_default_aspx.__Render__control13(HtmlTextWriter __w, Control parameterContainer) in d:\Program Files\HAP7\BookingSystem\Default.aspx:88 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +109 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +8 System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +31 HAP.Web.Controls.CompressJS.Render(HtmlTextWriter writer) in H:\Documents\Visual Studio 2010\Projects\CHS Extranet\HAP.Web\Controls\CompressJS.cs:29 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25 ASP.bookingsystem_default_aspx.__Render__control3(HtmlTextWriter __w, Control parameterContainer) in d:\Program Files\HAP7\BookingSystem\Default.aspx:82 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +109 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +8 System.Web.UI.Control.Render(HtmlTextWriter writer) +10 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +208 System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer) +173 System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +31 System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output) +53 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer) +40 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +208 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +8 System.Web.UI.Control.Render(HtmlTextWriter writer) +10 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +208 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +8 System.Web.UI.Page.Render(HtmlTextWriter writer) +29 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3060

Ive been running some tests on it, transferring the setup I have now to 2012. It will be a Summer project if I do it. Some more tests with the RTM version...

Just a heads up for anyone else installing/configuring SCCM - there is a blog series available via the link in my sig below...

Those who follow my blogs will remember that last Summer, I set about building a single platform system - based around Windows 7/Server 2008 R2. This post deals with the final part of the jigsaw relating to the Thin Client section - powered by Windows Thin PC (aka Windows 7 lite... it runs NT6.1) This post follows http://www.edugeek.net/blogs/thescarfedone/1108-remote-desktop-thin-client-part-2.html Introduction So – if you are using Terminal Server, or to give it its new name – Remote Desktop Services (RDS) – you will want to know about Single Sign-On (SSO). This is an authentication method that allows users with a domain account to log on once – so take the scenario where your users logon to a Thin Client as themselves, but you then want it to automatically trigger an RDS session. To implement single sign-on functionality in Terminal Services, ensure that you meet (and for production systems – exceed) the minimum requirements. The basic requirements needed to implement SSO are: You can only use single sign-on for remote connections from a computer running Windows Vista (or later) or Windows Server 2008 (or later) to a Windows Server 2008 (or later)Terminal Server. You must ensure that the user accounts that are used for logging on to the Terminal Server have appropriate rights to log on to both the Terminal Server and the Windows Vista/2008 (or later) client computer (ie. Add them to the Remote Desktop Users group via Group Policy or manually via Local Policy) Your client computer and Terminal Server must be joined to a domain. Understanding what the basic requirements are, more specific requirements for setting up SSO, is as follows: Servers: Windows Server 2008 (or later) Terminal Server with TS/RDS Server Role and TS/RDS Licensing Server Role enabled Windows Server 2008 (or later) Domain Controller (Active Directory) Proper Hardware Requirements Note: Although you can make a DC a Terminal Server, it is recommended that you split the roles and use separate servers based on the load that is expected. Obviously, whenever implementing a production system, you will want to make sure that you know what your application/traffic flows are and what load your users and the application puts on your network as well as the individual servers connected to it. Clients: Windows Vista (or Windows Server 2008 used as a client system) Remote Desktop Client (RDC) with Network Level Authentication (NLA) Support. NLA support is only available with RDC 6.0 and with Vista or 2008 (or later). Proper Hardware Requirements (exceed as needed) To configure the recommended settings for your Terminal Server, complete the following steps: Configure authentication on the Terminal Server, this can be done with AD, or locally on the server you want access to. Configure the computer running Windows Vista to allow default credentials to be used for logging on to the specified Terminal Server(s) on your network. You need administrative privileges on the Terminal Server you are configuring. Now that you know what you need, let us begin configuring SSO with Terminal Services. Configure Authentication on a Terminal Server First, verify you have a working Terminal Server. Check the Server Manager for the roles being installed and operational. Remember, you will need to have (at minimum), the Terminal Services Role and the Licensing Server Role installed and ready to configure SSO. Next, we will configure Single Sign-On (SSO) on the Terminal Server by opening Terminal Services Configuration. Go to Start => Administrative Tools => Terminal Services, and then click Terminal Services Configuration. Once you open the Terminal Services Configuration console, find the Connections pane. You should, at minimum, have the default connection in place which should be RDP-Tcp. To configure this (or any other connection) right-click the appropriate connection and then click Properties. Once you open the Properties dialog box, on the General tab 4, you can verify that the Security Layer value is set to either Negotiate or SSL (TLS 1.0). Negotiation will allow the system to ‘negotiate’ with a client what type of Security Layer is needed. On the Log on Settings tab, ensure that the Always prompt for password check box is not selected or checked, and then click OK to close the RDP-Tcp Properties dialog box. Now, you have configured authentication, next we will configure the default credential usage to be used with SSO. Allow Default Credential Usage for Single Sign-On (SSO) Now that we have authentication configured, we need to finish the process. To do this, you need to go to the client system (Vista, or 2008) and configure the Local Group Policy Editor. On your client computer open the Local Group Policy Editor. To open Local Group Policy Editor, go to Start, and in the Start Search box, type gpedit.msc and then press ENTER. In the Editor, look in the left pane and expand Computer Configuration => Administrative Templates => System => and then click Credentials Delegation. Double-click the Delegating Default Credentials setting to open it. Next, in the Properties dialog box on the Setting tab, select Enabled, and then select Show. In the Show Contents dialog box, click Add to add servers to the list. In the Add Item dialog box, type the prefix termsrv/ followed by the name of the Terminal Server you will be connecting too. Once you have added the server name, click OK to close the Add Item dialog box. Click OK a few times until you are back in the Local Group Policy Editor and close the MMC. Now you should be all ready to use SSO with Windows Server 2008 and 2008 Terminal Services.

Can you post your wlx.ini? I will also check the folder structure on mine tomorrow

Extrra debug information - so long as the information i put in the for max weeks in advance is a single digit (ie up to 9) - then it works. Go to 10 - then the error appears.

Hmmm.... there is still a discrepancy here somewhere! Im trying to find it... Ok... heres the scenario... In the HAP Config screen - Booking System - Administrators group selected as Staff-BookingsAdmin (thats our AD group that contains the higher level users) This correctly gives them the "book as someone else" option. It does not however over-ride the max days (cant tell if over-rides max bookings - but the info bar doesnt contain the entry "You have x bookings remaining this week"). So, go to Advanced permissions to add this as DOMAIN\username, which works - so long as its not during a holiday (but it is now - which throws a lovely error... shown at the end). Can you set it so that being in the extra admin group correctly handles max bookings and bookings in advance (no limit) as it does on Domain Admins; or can we bug fix that new dll? Oh... and I went back to that dll, which doesnt produce the error below - but then we are back to the max bookings limit again! The added or subtracted value results in an un-representable DateTime. Parameter name: value Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.ArgumentOutOfRangeException: The added or subtracted value results in an un-representable DateTime. Parameter name: value Source Error: Line 86: Line 87: var curdate, curres, curles; Line 88: var user = { <%=JSUser %> }; Line 89: var resources = <%=JSResources %>; Line 90: var availbookings = [ 0, 0 ]; Source File: d:\Program Files\HAP7\BookingSystem\Default.aspx Line: 88 Stack Trace: [ArgumentOutOfRangeException: The added or subtracted value results in an un-representable DateTime. Parameter name: value] System.DateTime.AddTicks(Int64 value) +9624435 System.DateTime.Add(Double value, Int32 scale) +136 HAP.Web.BookingSystem._new.get_JSUser() +3055 ASP.bookingsystem_default_aspx.__Render__control13(HtmlTextWriter __w, Control parameterContainer) in d:\Program Files\HAP7\BookingSystem\Default.aspx:88 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +109 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +8 System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +31 HAP.Web.Controls.CompressJS.Render(HtmlTextWriter writer) +4 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25 ASP.bookingsystem_default_aspx.__Render__control3(HtmlTextWriter __w, Control parameterContainer) in d:\Program Files\HAP7\BookingSystem\Default.aspx:82 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +109 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +8 System.Web.UI.Control.Render(HtmlTextWriter writer) +10 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +208 System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer) +173 System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +31 System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output) +53 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer) +40 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +208 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +8 System.Web.UI.Control.Render(HtmlTextWriter writer) +10 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +208 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +8 System.Web.UI.Page.Render(HtmlTextWriter writer) +29 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +100 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3060 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272

Yep - ive got 45 of them here... whats the problem?

Happy Birthday Chris... hope you have a great day. Awesome logo work again

Nope its fine to mention the site. Spiceworks is a help desk/inventory web application. It can either be paid for, or advert supported. Completely legit. There are lots of alternatives to it as well...

Yes, as far as I can tell - the same as Ive posted for Exchange 2010 will still work on 2007.

Ive posted a load of stuff on Windows ThinPC and RDP on my blog - from my new setup last summer. The start of it is here Windows Thin PC - Blogs - EduGeek.net. Im also using true SSO - just haven't finished the post on that, so will do that later and link it here.

Hi - sorry didn't see this, Im not getting the alert emails from blog comments. No, SCCM/WDS will only boot PXE if its own provider is set up. So - just installing the role isn't enough to take over the other software. Im guessing FOG? This is what I did - just disabled the PXE service when I wanted to carry on using FOG.

Please... if you could... Scenario, a meeting room being booked for a whole day - or remainder of the day

Im using Windows Auth - as Im one of your awkward ISA/TMG users. I will try taking it out just to confirm, but thats the change that seemed to make it work. What do you think of the feature request? Great work as always, thanks Stuart

Oooh, now that overview is snazzy. I like that a lot. Next release please indeed! Another request from me... (copied from the Advanced Bookings Permissions thread)... Can you add the ability for a booking to me made for a whole day, or for an existing one that you've just made to be copied to the rest of the day. Hope you can do it...