anyweb

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).

hi Denis ! 1. did you follow this guide 2. I prefer the build and capture process as it is 100% automated, however you can also do this 3. what collection did you deploy this task sequence to ? was it all systems ? if so now you know not to do this again and consider these ideas. keep up the good work cheers niall

also check out my new post here about installing the Primary Server in your heirarchy.

In Part 1 of this series we created our new LAB, we got the System Center 2012 Configuration Manager ISO and extracted it, then copied it to our Active Directory server. We then created the System Management container in AD, delegated permissions to the container, extended the Schema for Configuration Manager. We then opened TCP ports 1433 and 4022 for SQL replication between sites, installed some prerequisites like .NET Framework 4.0, added some features and then downloaded and installed SQL Server 2008 R2 SP1 CU6. We then configured SQL Server using SQL Server Management Studio for security and memory configurations prior to running the Configuration Manager 2012 setup to assess server readiness. Finally we installed a central administration site (CAS) and will now install our primary server. The primary server will be called P01 (P for primary, 01 as it's the first primary, if you were to have more primaries connected to your CAS, you could call the next one P02 and so on). Prior to installing our primary server I want you to set this server up the same way as you did the CAS, install the pre-reqs including .NET Framework 4.0, install SQL Server 2008 R2 SP1 CU6 and configure it (security and memory) before doing anything else. You do not need to extend the schema again that is a one time operation. The primary server (p01.server2008r2.lab.local) should therefore now have SQL installed and you should have copied the Configuration Manager 2012 source files from our active directory server AD1 to C:\Temp\CM12RTM before starting step 1 below. Note: Determine Whether to Install a Primary Site - The below is from Technet Use primary sites to manage clients. Consider installing a primary site for any of the following reasons: To manage clients directly. To increase the number of clients to manage. Each primary site can support up to 100,000 clients. To provide a local point of connectivity for administration. To meet organizational management requirements. For example, you might install a primary site at a remote location to manage the transfer of deployment content across a low-bandwidth network. Use the following information to help you plan for primary sites: A primary site can be a stand-alone primary site or a member of a hierarchy. A primary site only supports a central administration site as a parent site. A primary site only supports secondary sites as child sites and can support one or more secondary child sites. A primary site cannot change its parent site relationship after installation. Primary sites are responsible for processing all client data from their assigned clients. When a primary site is installed, it automatically configures database replication with its designated central administration site. Primary sites use database replication to communicate directly to their central administration site. You can install typically used site system roles when you install a primary site. For a list of site system roles that are supported on primary sites, see Planning Where to Install Sites System Roles in the Hierarchy. Note: Each primary site management point can support up to 25,000 computer clients. To support 100,000 clients you must have at least four management points. Do not place management points across a slow link from their primary site server or from the site database server. Each primary site can support up to 10 management points. When you have more than four management points in a primary site, you do not increase the supported client count of the primary site beyond 100,000. Instead, any additional management points provide redundancy for communications from clients. For more information about this topic see Site and Site System Role Scalability on Technet. Hardware Requirements Note: For detailed hardware requirements for site servers both standalone and in a hierarchy please see the following page on Technet. The below information is summarised from Technet and should be used as a reference in planning for your Primary site hardware requirements. Primary site in a hierarchy (Local SQL Install) Up to 50,000 clients SQL Server is installed on the site server computer The suggested hardware for the above is as follows:- 4 cores (Intel Xeon 5140 or comparable CPU) 16 GB of RAM 300 GB of hard disk space for the operating system, Configuration Manager, SQL Server, and all database files. Primary site in a hierarchy (Remote SQL Install) Up to 100,000 clients SQL Server is remote from the site server computer Site Server: 4 cores (Intel Xeon 5140 or comparable CPU) 8GB of RAM 200 GB of disk space for the operating system and Configuration Manager. Remote SQL Server: 8 cores (Intel Xeon E5504 or comparable CPU) 32 GB of RAM 550 GB of hard disk space for the operating system, SQL Server, and all database files. Determine the Distribution Point Infrastructure At least one distribution point is required at each site in the Configuration Manager hierarchy. By default, a primary site server is configured as a distribution point. However, assign this role to a remote site system and remove it from the site server if possible. This role assignment reduces the resource requirements and improves performance on the site server, and also assists in load balancing. The distribution point site system role is automatically configured on the secondary site server when it is installed. However, the distribution point site system role is not required at secondary sites. Clients connect to distribution points at the parent primary site if one is not available at the secondary site. As you configure your distribution points with assigned boundary groups, consider the physical location and network connection speed between the distribution point and site server . Step 1. Start the System Center 2012 Configuration Manager setup Note: Perform the following on the Primary server (P01) as SMSadmin It is important to note that the user you use to run the Configuration Manager setup wizard has the correct rights assigned, if you are using the domain user, SMSadmin then you should be ok. We added this user as a Local Administrator of both the CAS and P01 servers in Step 1 of Part 1. If you try to run the setup wizard as a user that doesn't have the correct rights or if you are logged onto this computer as the local administrator and not a domain user, you may see all sorts of warnings in the server readiness check including Active Directory Schema warnings even though you've extended the schema. Therefore please take note of the following requirements for the user prior to running setup and login as that domain user (server2008r2\SMSadmin). Verify the user that runs Setup has the following security rights: Local Administrator rights on the central administration site server. Local Administrator rights on the remote site database server for the central administration site, if it is remote. Sysadmin rights on the site database of the central administration site. Local Administrator rights on the primary site computer. Local Administrator rights on the remote site database server for the primary site, if it is remote. User name associated with the Infrastructure Administrator or Full Administrator security role on the central administration site. Note: The hotfix described in KB2552033 must be installed on site servers that run Windows Server 2008 R2 when client push installation is enabled. As we will configure client push on this primary, you must install that hotfix. Browse to C:\Temp\CM12RTM on your Primary server, and double click on splash.hta the System Center 2012 Configuration Manager Setup screen appears. click on Assess Server Readiness, if you did everything outlined above then the only warning (in yellow, errors are in red) you'll see is about WSUS SDK on site server, and that is ok to ignore as we'll be installing it later on in this series. click Ok and then click on Install to start the setup wizard, answer yes to any UAC prompts.. review the wizard Before you Begin page...and click next The option we need will already be selected (Install a Configuration Manager primary site), do NOT place a checkmark in the box below as this will install a standalone site instead of allowing us to join our Primary to our Central Administration Site server. If you want to install a standalone primary then read this guide instead. enter your Product Key or choose the evaluation option, yes you can upgrade from evaluation to full version (read this post from Ronni). Accept the Microsoft Software License Terms followed by the Prerequisite Licenses The Prerequite Downloads screen offers you the choice to use previously downloaded files, as we already downloaded them when installing our CAS I copied these files to C:\Temp\downloads click next and they'll be verified.. and you get to see the Server Language Selection closely followed by the Client Language Selection, choose the language that you want displayed on the display language of the client computer (eg: if your client computers are in Swedish, choose Swedish). You can always modify these options later by running Setup again and choosing Site Maintenance. for Site and Installation Settings fill in your desired Site Code (P01) and name, and install it to D:\, make sure you are happy with the choices as you can't change them later... now you get to join it to our CAS in the Primary Site Installation screen, type in the FQDN of your CAS server (if you want it to be a standalone you could choose that option now...) next we have the Database Information, it should auto populate followed by the SMS Provider settings, you can have multiple SMS Providers depending on your needs but we will just be using one in this LAB next we get to configure Client Computer Communication Settings (HTTP or HTTPS). Select Configure the communication method on each site system role. and the Site System Roles screen appears, note that the site server Computer Account must be a member of the Local Administrators Group in order to install these roles. and next you get the Customer Experience Improvement Program Configuration options review the Settings Summary before seeing our Prerequisite Check being performed again, click Begin Install to start installing our Primary Server and off it goes ! Tip: click on View Log to see the C:\ConfigMgrSetup.log file scrolling by in real time. CMTrace should be run once first to associate itself with log files. You can find CMTrace in the ConfigMgr media which you copied to C:\Temp\CM12RTM\SMSSetup\Tools\ Core setup will be done in approx 37 minutes on reasonable hardware (read: a nice laptop) but you want to wait until all the components listed are green before patting yourself on the back for a job well done and that takes considerably longer. Note that the time doesn't progress after core setup, you can review the log for details of what was actually done. After that you can close the wizard and start the Configuration Manager console on your newly installed primary. navigate to Monitoring and Site Heirarchy in the console, Tip: you can move your mouse cursor on the link between CAS and P01, or point it directly to either of the site servers to see how replication is going. You can also review the SMS_REPLICATION_CONFIGURATION_MONITOR component status or review the rcmctrl.log to get more details of how replication is progressing. congratulations, you now have a System Center 2012 Configuration Manager 2012 hierarchy !. Note: Setup automatically configures the-sender address to use the computer account for the primary site server. This account must have Read, Write, Execute, and Delete NTFS file system permissions on the SMS\Inboxes\Despoolr.box\Receive folder on the central administration site server. Also, your security policy must allow the account Access this computer from the network rights on the central administration site. After Setup completes, you can change the account to a Windows user account if required. For example, you must change the account to a Windows user account if your central administration site is in a different forest. For more information about communication requirements across forests, see Planning for Communications Across Forests in Configuration Manager. In the next part we will configure Discovery methods and Boundaries.

can you verify the SQL version please in sql management studio

well i think your issues are related to this question is, why did you do this and not use the boot wim's that are installed as part of configmgr setup ?

what version of SQL did you use when installing the server ? did you follow my guides or not (to the letter) ?