anyweb

spread the word !

take a look at Planning for Sites and Hierarchies in Configuration Manager here on Technet first. Then, if you decide against a standalone primary setup (which can have secondaries and dp's) you can read my hierarchy setup guide here to further understand the do's and don'ts.

if you want to upgrade ConfigMgr 2007 then you have to use the side-by-side approach as I explain in this post. using Configuration Manager 2012 RC in a LAB - Part 14. Performing a side-by-side Migration from Configuration Manager 2007 Part 14. Performing a side-by-side Migration from Configuration Manager 2007. [January 27th, 2012]

there is Cu6, look at my using System Center 2012 Configuration Manager - Part 1. Installation - CAS Part 1.Installation - CAS the download link is there

CU6 is listed as the supported install version now

D:\ is just a suggestion, you can put it wherever you want, but seeing as most people frequently run out of space on C:\ due to poor planning i'd suggest another drive letter other than C:\, also SQL is IO intensive (disk read/write) and if possible you should try and install on it's own hard disc. Also you don't want to mix SQL or other programs (Configuration Manager) with the operating system, think about performance ..

well in my example above SMSadmin is the user running the configmgr console and that user is a local administrator of the same box, are you performing this as a user that has local administrative permissions on that server or has the user rights to read/write to that folder (the package source folder mentioned in your log file)

the build and capture method is definetly recommended as its 100% automated, the method above requires manual steps, but achieves the same result

good stuff, so for everyone else i'll explain the solution, create a Configmgr client Package (from definition) and use that package for the setup windows and configmgr step and not the built in one, otherwise you cannot change from 'download' to 'access' cheers niall

which configmgr client are you using in the task sequence ? the built in one, or one you created yourself (from a package from definition) ? if you use the build in package then you cannot change it's properties, instead, create a new one from 'create package from definition' and then make the appropriate changes to that package and use that pacakge in your task sequence

i would definetly upgrade to CU6, stop all CCM releated services then do the upgrade, reboot

When you install new computers it would be nice to be able to easily name the computer as part of the deployment, otherwise the new computer could end up with a name like MININT-XRGHJTF unless you import it into Configuration Manager first. You can script around this in your task sequence or use web services or HTA's but the easiest method of all is to set a Collection variable called OSDComputerName. This method does not require any scripting all you need to do is to Enable Unknown Computer support in the Distribution Point PXE tab settings. To prompt the end user to enter a computer name In Configuration Manager 2012 by using the OSDComputerName variable you first need to think about the computers you are aiming this at, and in this case the computers are unknown computers, that is, they are unknown to Configuration Manager. Step 1. add the collection variable Now that we know that they are unknown we need to select the Unknown Computers collection called All Unknown Computers. Right click and choose Properties. select the Collection Variables tab and click on the Yellow star burst button as shown below enter the following variable name when prompted OSDComputerName, remove the checkmark from Do Not Display this value in the Configuration Manager console as in the screenshot below click ok and apply so that it looks like this Step 2. Make sure you have Deployed a task sequence to the Unknown Computers collection Verify that you have deployed your chosen task sequence to the Unknown Computers collection by selecting the task sequence and clicking on the Deployments tab. The deployments listed should include one for the All Unknown Computers collection as shown below. If not, then create a new deployment for the task sequence and choose the All Unknown Computers collection for that deployment. Step 3. PXE boot a new computer PXE boot a new computer. Press F12 when prompted Note: make sure the computer is NOT present in Configuration Manager prior to this, either as a previous computername or as an UNKNOWN object, if it is, highlight it in All Systems and delete it. select your task sequence and click next now you will see a Task Sequence window called Edit Task Sequence Variables double click on OSDComputerName, the following should appear type in a computername click ok and the computername value should be listed to the right of the variable name as shown below click next and the task sequence completes as normal Step 4. Verify that it worked Now that the Task Sequence is complete you can logon to your computer, bring up the computer properties and note the computername is what you entered earlier. the variable is set during the Apply Windows settings step of the task sequence and you can see the collection variable being added in the SMSTS.log file (found in C:\Windows\CCM\Logs) that's it, I told you it was easy ! cheers niall

what exact version of SQL server did you install ? when running the SPLASH.HTA are you logged in as a domain user or as local administrator ?

check what antimalware policy is listed on the client

what accounts are the sql services running as ? are you running sql server 2008 r2 sp1 cu6 ?

not following you, what are you trying to migrate from and to ?

using a domain admin account for the SMSAdmin user would be a huge security risk and is definetly not best practice, create the SMSadmin user using any username you wish (SMSadmin is easy to remember..) and the user should just be a regular domain user, adding them as local administrator on the configuration manager server(s) is sufficient for our needs. the other accounts listed as used to get the job done, test users are for testing things, domjoin for joining the domain during OSD

please read this post and hotifx KB article http://www.windows-noob.com/forums/index.php?/topic/3718-adding-a-hotfix-to-the-setup-windows-and-configmgr-step-in-a-task-sequence/

what does your smsts.log file say, have you applied the kb2509007.. hotfix ? http://www.windows-noob.com/forums/index.php?/topic/3718-adding-a-hotfix-to-the-setup-windows-and-configmgr-step-in-a-task-sequence/

yes run it once then you'll have the deployment package created, then you can right click on it and choose Disable. You can reference that package (your Endpoint Protection Definition Updates package) in the new ADR created directly afterwards. i.e. you go through the same process twice, first time you Create a new deployment package, second time you point to that package

ok so to confirm, you had a configmgr 2007 client installed on this server and that was the reason it was complaining ?

Summary: Microsoft’s decision to remove support for playing DVD movies in Windows 8 has caused some confusion. If the VLC media player can provide DVD support for free, why can’t Microsoft? For starters, Microsoft isn’t French. Microsoft announced this week that Windows 8 will not support playback of DVD movies unless you explicitly add software that supports that feature. The economic reasons for doing so are compelling (see Microsoft’s follow-up FAQ for details), but it’s also a potentially disruptive move for some Windows enthusiasts. So it’s not surprising that some of the initial reactions have been heated and even angry. I’ll look at the big numbers and walk through the math in a follow-up post. But I wanted to interrupt the discussion here to answer a question that several people have asked. “Microsoft says the cost of DVD playback adds up to several dollars,” the argument goes. “But I can download the VLC player for Windows and get DVD playback for free. How come VLC can do it and Microsoft can’t?” Welcome to the wonderful world of software licensing, where today we get to see a real-world example of the differences between commercial software and free software published under an open source license. Any commercial product—hardware or software—that plays back DVDs has to have a license to a handful of software components that are protected by patents. In particular, you need access to the following: An MPEG-2 decoder. The licensing rights for the MPEG-2 standard are made up of a pool of patents contributed by their inventors. The pool itself is managed by MPEG LA, which collects and distributes royalties on behalf of the patent owners, under a master license agreement. Those rights cost $2 per device. The maker of a cheap DVD player sold at Costco pays $2 per unit for the MPEG-2 rights. Microsoft pays An OEM PC maker who licenses Windows from Microsoft must pay $2 in MPEG-2 licensing fees to enable DVD playback in every copy of Windows 7 Home Premium, Professional, and Ultimate. [Edited to clarify payment requirements] Dolby Digital audio support. This decoder, which is required for DVD movie playback, has to be licensed from Dolby Laboratories, Inc. The licensing schedule isn’t public, but in its annual report for 2011 Dolby revealed that it collected $124 million in licensing fees from Microsoft for the year, with most of that revenue generated from Windows 7. My back-of-the-envelope calculations suggest that Dolby gets at least 50 cents and as much as a dollar for every Windows PC sold. Microsoft, Apple, Panasonic, Sony, Samsung, and other companies that make DVD players (hardware and software) have to pay those license fees for every unit they deliver to a customer, which is why you don’t see very many free DVD players. The noteworthy exception is the VLC media player, which proudly bills itself as “a free and open source cross-platform multimedia player and framework.” It explicitly lists DVD as a supported format. How can that be? Well, on its “Legal concerns” page the makers of VLC open with a proud declaration: “VideoLAN is an organization based in France,” and “French law … is the only one to be applicable.” If you skip to the bottom of the English portion of the page, you see why that matters. This is VideoLAN’s argument: Patents and codec licenses Neither French law nor European conventions recognize software as patentable (see French section below). Therefore, software patents licenses do not apply on VideoLAN software. The two software libraries that enable DVD and Blu-ray playback in VLC are libdvdcss and libaacs, both of which get their own legal justifications (the bold-faced words are in the original): libdvdcss is a library that can find and guess keys from a DVD in order to decrypt it. This method is authorized by a French law decision CE 10e et 9e sous­sect., 16 juillet 2008, n° 301843 on interoperability. NB: In the USA, you should check out the US Copyright Office decision that allows circumvention in some cases. VideoLAN is NOT a US-based organization and is therefore outside US juridiction. [sic] […] libaacs is a research project and has an interoperability purpose (see above point). Moreover, libaacs DOES NOT provide any decryption key. It is based on the official public AACS specification only. Update: Via Twitter, VideoLAN notes that “libaacs is not yet shipped with VLC. We are waiting for remarks from the French DRM authority.” Their comments include a link to this article (English translation). I’m sure if one were to ask a lawyer for one of the patent holders in the MPEG-2 or AACS pools, one would get a very spirited argument about the validity of those arguments. That argument would probably invoke the anti-circumvention provisions of the United States’ Digital Millennium Copyright Act. But VLC can get away with it primarily because it is a nonprofit organization based outside the reach of the United States legal system and not worth pursuing. A maker of commercial DVD playback hardware or software would be sued in a heartbeat if they tried to distribute products based on those freeware projects. They’d also run afoul of the General Public License if they tried to include the code in their closed-source, commercial products. But the VLC project is hardly a rogue player. In fact, as I noted in a 2010 post, Microsoft has provided financial support for VLC: Anyone can write a media player for Windows and can build in support for whatever media formats they want. No one is “required” to use Windows Media Player—exactly the opposite…. One alternative is VLC, which I have praised before…. In an e-mail to me, one of the core developers of VLC specifically praised Microsoft last year for its assistance, noting that “Microsoft … funded our Windows 7 compatibility program participation.” Any OEM that includes a DVD player in a new Windows 8 PC will undoubtedly include a licensed DVD Player, such as the Metro version of PowerDVD that CyberLink announced at CES earlier this year. (If PowerDVD is smart, they’ll include both the Metro and desktop versions with Windows 8.) You’ll also have an assortment of commercial programs to choose from. The good news is that as a consumer you can count on the continued availability of VLC as a free DVD (and Blu-ray) playback alternative if you don’t want to pay for the Media Center Pack. And the project continues to evolve. Earlier this week, VideoLAN boasted via its official Twitter account: “by the time Windows 8 is out, we will have even better Blu-Ray support!” via ZDnet > http://www.zdnet.com/blog/bott/if-vlc-can-ship-a-free-dvd-player-why-cant-microsoft/4962?tag=content;search-results-river

While it's technically a regression, and while it will surely make those of us who remember having to install DVD support on Linux from third-party repositories smile, it's still a major change and a sign of things to come: Windows 8 will ship without support for DVD and Blu-ray playback. Back in the day, you had to manually enable DVD playback after installing Linux. Distributions based out of the US were unable to include the required libdvdcss (or libdvdcss2), so users had to manually install the package afterwards. Smaller distributions, or those based outside of the US, were more liberal with including libdvdcss. The end result was loads of articles on the web detailing how to enable DVD playback support on Linux. It was a ritual of some sort. In a way, it's kind of poetic justice that Windows users will now have to jump through the same hoops. To cut costs, and since its use was declining anyway, Windows 8 will ship without support for DVD and Blu-ray playback. To enable it, you have to buy/install Windows Media Center, or rely on one of the many third party solutions. The same also applies to support for DBV-T/S, ISDB-S/T, DMBH, and ATSC. "Globally, DVD sales have declined significantly year over year and Blu-ray on PCs is losing momentum as well. Watching broadcast TV on PCs, while incredibly important for some of you, has also declined steadily," Microsoft details, "These traditional media playback scenarios, optical media and broadcast TV, require a specialized set of decoders (and hardware) that cost a significant amount in royalties." This should reduce the cost of a Windows license, and considering Windows 8 has a tablet-focus, it makes sense not to force OEMs to pay for something tablets won't have anyway (optical drives). It's a good thing for me - I haven't had an optical drive in any of my PCs for years, and I wouldn't be surprised if the same applies to more of you. Just ask yourself: when was the last time you really used your optical drive? It's also a sign of something larger within Microsoft: the company has become incredibly willing to cut cruft from their operating system, even when it comes to support for hardware. This is a good sign, since if there's one thing that's held Microsoft and Windows back, it's that. As far as the entire industry goes, it's obvious that optical media are on their way out. Apple never even supported Blu-ray to begin with, and with more and more laptops being sold without an optical drive, it only makes sense to start phasing it out. Let's face it - it's never been a particularly good storage medium, in terms of capacity, reliability, and speed. So, raise a cup of coffee, and good riddance, I say. via osnews.com > http://www.osnews.com/story/25910/Windows_8_to_ship_without_DVD_Blu-ray_support

then script it,. add a Run Command Line step in your task sequence to do as follows:- cmd /c net localgroup "Administrators" domain\%USERNAME%" /add %USERNAME% is a variable but you can hard code it

currently the computer i use for LAB work (including pretty much all of the current CM12 series) is a HP Elitebook 8560W, with 16GB ram and core i7 2360qm (4 cores, 8 logical processors), 2 ghz, it has two hard discs, one SATA 700GB (sorry Thomas, i was wrong, it wasnt a 1TB) and one 240GB SSD drive in the modular bay. I have a 1.3TB USB 3.0 disc connected also as it has a load of virtual machines running on it (i have both Configuration Manager 2007 and 2012 labs, standalone and heirarchy).