anyweb

you are not making much sense, are you trying to do something with WDS that is not working ?

nice post Peter, keep it up, pinned !

for driver integration with ConfigMgr, Dell does a brilliant job of producing CAB files for driver importing, if only the other vendors followed suit

you can only install WDS on a server operating sytem. (windows server 2003 and onwards...)

under advertisements you can see what has been advertised (made available/targeted) and what collections they are targeted to

ok so is your network card your first boot device in the bios ? then no need to press F12 twice, you only need to press F12 when it states 'press F12', that's the point i'm trying to make, F12 on most dells for example initiates a one time boot menu where you can select Network boot...

can you post your smsts.log file ?

i blogged about a side-by-side migration today, hope it helps ! http://www.windows-noob.com/forums/index.php?/topic/4926-using-sccm-2012-rc-in-a-lab-part-14-performing-a-side-by-side-migration-from-configuration-manager-2007/

is your boot image 64 bit or 32 bit ?

ok can you attach your SMSTS.log and any other logs in ZIP format here so that I can review them ?

In Part 1 of this series we got our AD and SCCM servers ready, and then we installed System Center 2012 Configuration Manager as a standalone Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles necessary for the following Configuration Manager 2012 functionality, Software Update Point (SUP) and Operating System Deployment. In Part 3 we configured the server further by Enabling Discovery methods and creating Boundary's and Boundary Groups. In Part 4 we configured Client Settings, Added roles and Distributed the Configmgr Client to our Computers within the LAB, then in Part 5 we enabled the Endpoint Protection Role and configured Endpoint Protection settings and targeted a collection called All Windows 7 Computers with these settings and policies. In Part 6 we configured our SUP further to Deploy software updates to our All Windows 7 Computers and Build Windows 7 X64 collections. In Part 7 we used the Build and Capture process to create our Base Windows 7 X64 wim image. In Part 8 we created a USMT 4 package to migrate the users data using hardlinking and then we imported the captured image into ConfigMgr and created a Deploy Windows 7 X64 task sequence. We created a Deploy Windows 7 X64 Collection and set some User Device Affinity collection variables. In Part 9 we created an Application, and created a deployment type for that application to only install if the Primary User was True for that device (User Device Affinity), we then copied our Task Sequence (duplicated it), deployed the new Task Sequence, added a computer to the new collection and then PXE booted the computer to the Deployment Menu. In Part 10 we monitored the Deployment process in a lot of detail to how UDA sent state messages and we verified that our application installed on the users Primary Device, in addition we modified our collection variables, and added a prestart command to our boot image to prompt for the SMSTSUdaUsers. In Part 11 we setup the Reporting Services Point Role and verified that reporting was working. In Part 12 we demonstrated a new feature in ConfigMgr which allows us to Patch operating system WIM images using Offline Servicing. This means that you can apply Windows Updates by using Component-Based Servicing (CBS) to update the your previously captured WIM images. In Part 13 we looked at how Role Based Administration is used within ConfigMgr and we created a new custom role to allow a user (or users within a Security Group) to view Software Update Reports. This is useful because you will probably want one team to take care of configuring and deploying software updates, and to grant another (Management etc) the capability of reviewing Compliance Reports. Now we will perform a side-by-side migration from Configuration Manager 2007. For recommended reading about migrating to Configuration Manager 2012 and best practise advice, please refer to the following links from Technet:- Introduction to Migration in System Center 2012 Configuration Manager Planning for Migration to System Center 2012 Configuration Manager Configuring Migration to System Center 2012 Configuration Manager Operations for Migrating Configuration Manager 2007 to System Center 2012 Configuration Manager Security and Privacy for Migration to System Center 2012 Configuration Manager Some key points about migration. Before you migrate any data from Configuration Manager 2007, you must first install and configure the System Center 2012 Configuration Manager hierarchy. You should not try to recreate or mirror your hierarchy from the source to the destination. Plan to only migrate what you need in the new hierarchy and focus on the new features and design of Configuration Manager 2012. You cannot upgrade from SMS 2003 to Configuration Manager 2012, the only supported method is to migrate from SMS 2003 to Configuration Manager 2007 (in-place or side-by-side) and then perform a side-by-side migration to Configuration Manager 2012. Or, you could call it a day on SMS 2003 and start fresh with Configuration Manager 2012. You cannot do an in-place upgrade from Configuration Manager 2007 to Configuration Manager 2012. If you want to migrate your data and objects from Configuration Manager 2007 to Configuration Manager 2012 then you have to perform a side-by-side migration. Your source hierarchy (Configuration Manager 2007) must be at Service Pack 2 level. You must specify the top level site of your source heirarchy (Configuration Manager 2007). When System Center 2012 Configuration Manager gathers data, the following network protocols and ports are used: NetBIOS/SMB – 445 (TCP), RPC (WMI) - 135 (TCP), SQL Server - 1433 (TCP). As a result, ensure that they are not blocked between your source and destination servers. To perform the migration, the account used in Configuration Manager 2012 console must be a member of the Full Administrator security role. This security role grants permissions to manage all migration operations, which includes the creation of migration jobs, cleaning up, monitoring, and the action to share and upgrade distribution points. If you have mixed collections containing users and computers in Configuration Manager 2007, separate them into separate collections prior to the migration. Site codes must be unique. You cannot re-use site codes from a source hierarchy (Configuration Manager 2007) to the destination hierarchy (Configuration Manager 2012). When you migrate content, it is the compressed source files that migrate to System Center 2012 Configuration Manager. We can migrate the following: Collections, Advertisements, Boundaries, Software distribution packages, Virtual application packages,Software Updates, Operating System Deployment, Desired Configuration Management, Asset Intelligence, Software metering rules. Ok now that we are aware of the above, and after reviewing the pages on Technet for best practise advice, let's do a simple migration in our LAB. This LAB has a Configuration Manager 2007 server configured with a separate boundary from our Configuration Manager 2012 site boundaries. Both sites are within the same AD Forest. Both sites are standalone primaries. For this LAB we will migrate some Software Update items. Before doing so let's take a very quick look at what the software updates collection structure looks like in our Configuration Manager 2007 site. Step 1. Specify Source Hierarchy Perform the following on your Configuration Manager 2012 server as SMSadmin. In the Administration workspace, expand Overview and select Migration, as we havn't migrated anything yet it's going to look pretty bland. We need to specify the source hierarchy in order to establish a connection between the source (CM07) and destination (CM12) servers, so click on Specify Source Hierarchy in the ribbon. when the wizard appears we need to specify the Top-Level Configuration Manager 2007 site server. So fill in those details. Next we need to specify the Source site account to use to access the SMS Provider for that site server. The account needs read permissions on all source site objects. In our LAB we will specify the CM07Admin account which was the same account used to install that site server. So click on the Set drop down menu and select New Account. Input your account credentials and click on Verify Click on Test connection make sure you see a successful connection before proceeding. We will use the same account as the source site SMS provider account, so click on OK to exit this wizard. after clicking ok you'll see a window informing you that it is gathering data from the source site a few minutes later and it's done, close that window. at this point we can now see that our migration summary window has populated with some information. Note: You can start and stop the data gathering process by using the Gather Data Now, and Stop Gathering Data actions in the Configuration Manager console. Step 2. Create a migration job Perform the following on your Configuration Manager 2012 server as SMSadmin. In the ribbon click on Create Migration Job When the Migration Job wizard appears give it a name that is descriptive of what we are planning on migrating. Notice that in the drop down menu for Job Type we have three choices Collection Migration Object Migration Objects modified after migration In this case we are going to migrate collections, so we will name this migration job as follows:- Migrate Software Update Management Collections Click next and a list of collections that can be migrated to Configuration Manager 2012 are displayed. As we are only interested in migrating our Software Update collections, let's select them. If you have advertisements associated with these collections (Deployment Management Tasks) then they will be migrated also if you select Migrate objects that are associated with the specified collections. next we get to select objects that we want to migrate. Look through what is highlighted and decide if you really want to migrate it or not, this is a LAB so we'll let everything stay selected. for Content ownership, specify which site in your Configuration Manager 2012 hierarchy will be the designated owner of the content, in our LAB we have standalone primaries so just click next. next you can specify the Security Scope to be applied to the migrated objects, select the Default option. (I will return to Security Scopes in a separate Part). if any collections need to be limited to All Systems or All Users then they'll appear here, we are ok so lets proceed. On the Site Code Replacement screen you may see collections that are based on Queries that are limited to Site codes, we don't have any in this LAB so nothing appears, but if you have any queries like this in your LAB then you'll see those collections listed here. What it's telling you is that you'll have to edit the queries to point to the new site code. and now you get to review the information, you can save it to a file (recommended) which is a plain text file that lists things that you should be aware of. Save the file, read it. Action it. Next you can decide to run the migration job now (default) or schedule it until later. We want to migrate now so let's do that. Note that we don't want any new deployments being enabled after an advertisement is migrated so verify that setting is not selected (by default it is not selected). This will mean that you have to manually enable the deployments in Configuration Manager 2012, but that's ok isn't it. click next at the summary and let the wizard do its work...then review the confirmation screen Step 3. Monitor your migration job and resolve issues found. Perform the following on your Configuration Manager 2012 server as SMSadmin. In the console click on Migration Jobs and you'll see the status of our newly created migration job, in the screenshot below it is still running. After a while it should complete, note that the status in our LAB says Failed. Before we find out why, let's review the information that the job shows us in the summary, in particular let's review the Object Migration Progress. We can see that it has migrated 2 objects, 7 failed and 3 were skipped. Click on the Objects in Job tab to get specific information about the status of migration. The objects that are skipped are empty collections (empty collections are NOT migrated). The failed objects are more interesting and you can select each object that has failed and read its corresponding message (by scrolling to the right) to find out what you need to do to fix it. for example, the following message appears on one of the objects:- Great, now we know what's wrong and how to fix it. The message in this example is telling us that the products synched are not matching on the destination (it doesn't understand how to deal with them) so let's verify how our Products are configured on both sites, CM07 on the left, CM12 on the right, see the difference ? They should both be identical prior to running the Migration Job, this is an important lesson for you :-) So correct the problem, do a Software update sync on CM12 and run your migration job again. Repeat this process for each failed message until all messages have been actioned upon. Note that you will most likely have to go and Gather Data again particularly if the logs/messages tell you to do so. But once you've resolved the problems your migration should complete as per the screenshot below. and here's what did get migrated, I may go into further details about migrations in a later post, notice the migrated Advertisments become Deployments. another view in Software Library, Software Updates don't forget to enable any Deployments that you want enabled Finally, you can review the Migration Summary screen to get an overview of your total Migration Progress (you'll need to create more migration jobs to get the other objects if you want them Troubleshooting note You can review the migctrl.log and smsprov.log log files for more information about problems with your migration see screenshot below. They will give you more information about what is going on behind the scenes.

In Part 1 of this series we got our AD and SCCM servers ready, and then we installed System Center 2012 Configuration Manager as a standalone Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles necessary for the following Configuration Manager 2012 functionality, Software Update Point (SUP) and Operating System Deployment. In Part 3 we configured the server further by Enabling Discovery methods and creating Boundary's and Boundary Groups. In Part 4 we configured Client Settings, Added roles and Distributed the Configmgr Client to our Computers within the LAB, then in Part 5 we enabled the Endpoint Protection Role and configured Endpoint Protection settings and targeted a collection called All Windows 7 Computers with these settings and policies. In Part 6 we configured our SUP further to Deploy software updates to our All Windows 7 Computers and Build Windows 7 X64 collections. In Part 7 we used the Build and Capture process to create our Base Windows 7 X64 wim image. In Part 8 we created a USMT 4 package to migrate the users data using hardlinking and then we imported the captured image into ConfigMgr and created a Deploy Windows 7 X64 task sequence. We created a Deploy Windows 7 X64 Collection and set some User Device Affinity collection variables. In Part 9 we created an Application, and created a deployment type for that application to only install if the Primary User was True for that device (User Device Affinity), we then copied our Task Sequence (duplicated it), deployed the new Task Sequence, added a computer to the new collection and then PXE booted the computer to the Deployment Menu. In Part 10 we monitored the Deployment process in a lot of detail to how UDA sent state messages and we verified that our application installed on the users Primary Device, in addition we modified our collection variables, and added a prestart command to our boot image to prompt for the SMSTSUdaUsers. In Part 11 we setup the Reporting Services Point Role and verified that reporting was working. In Part 12 we demonstrated a new feature in ConfigMgr which allows us to Patch operating system WIM images using Offline Servicing. This means that you can apply Windows Updates by using Component-Based Servicing (CBS) to update the your previously captured WIM images. Now we will look at how Role Based Administration is used within ConfigMgr and we will create a new custom role to allow a user (or users within a Security Group) to view Software Update Reports. This is useful because you will probably want one team to take care of configuring and deploying software updates, and to grant another (Management etc) the capability of reviewing Compliance Reports. Note: From this point on, all parts in this series will be created using Configuration Manager 2012 Release Candidate 2 unless otherwise specified. For more information about Role Based Administration and for best practise advice please review the following:- Technet:- Security: Role-Based Administration Section of Whats new in Configuration Manager 2012 here Planning for Security in Configuration Manager 2012 - http://technet.micro...y/gg712284.aspx Introducing Role-Based Administration in System Center 2012 Configuration Manager - http://blogs.technet...on-manager.aspx Step 1. Understanding Role Based Administration In Configuration Manager 2007, administrative access to site resources is controlled by using class and instance security settings that are verified by the SMS Provider computer to allow access to site information and configuration settings. System Center 2012 Configuration Manager introduces role-based administration to centrally define and manage hierarchy-wide security access settings for all sites and site settings. Instead of using individual class rights, role-based administration uses security roles to group typical administrative tasks that are assigned to multiple administrative users. Security scopes replace individual instance rights per object to group the permissions that are applied to site objects. The combination of security roles, security scopes, and collections allow you to segregate the administrative assignments that meet your organization requirements and this combination defines what an administrative user can view and manage in the Configuration Manager hierarchy. Role-based administration provides the following benefits: Sites are no longer administrative boundaries. They were with Configuration Manager 2007. You create administrative users for the hierarchy and assign security to them one time only. You create content for the hierarchy and assign security to that content one time only. All security assignments are replicated and available throughout the hierarchy. There are built-in security roles to assign the typical administration tasks and you can create your own custom security roles. Administrative users see only the objects that they have permissions to manage. You can audit administrative security actions What roles are included ? The following 14 built in security roles are included:- Operations Administrator Full Administrator Infrastructure Administrator Security Administrator Software Update Manager Read-Only Analyst Remote Tools Operator Operating System Deployment Manager Application Deployment Manager Application Author Application Administrator Asset Manager Endpoint Protection Manager Compliance Settings Manager Step 2. Implementing a custom security role. Perform the following on your Configuration Manager 2012 server as SMSadmin. In the ConfigMgr console, click on Administration and expand Security, click on Security Roles. The 14 built-in roles appear. We want to create a custom security role to allow users assigned to that role to read Software Update Reports. As there is no option to create a blank new role, we must use the Copy function to create our new security role. Select the built-in Software Updates Manager role, right click and choose Copy. When the Copy Security Role wizard appears, give the new role a name based on the function, you can name the new role as follows:- SUM Reports Reader it's also a good idea to fill in a Description of the role as per the screenshot below, notice all the predefined permissions assigned to the Software Updates Manager role appear selected in the Permissions pane. We will edit these to only leave those permissions that are required to run reports. using the Customize the permissions for this copy of the security role, expand any permission not required and change it from YES to NO (you can double click on each one to change). For example, expand the Alerts permissions and set them all to NO as none of these permissions is required to read reports. Configure the Permissions so the only the following are set to Yes Site: Read Software Updates: Read, Run Report Click OK when done, the custom SUM Reports Reader role now appears in your console. Step 3. Create a Global Security Group in Active Directory Perform the following on your Active Directory Domain Controller server as Domain Administrator. Now that we have created our custom security role, we want to assign users to that role. In Active Directory Users and Computers create a new Global Security Group called Software Updates Management Report Readers as per the screenshot below. To create a new global security group, right click on Users, select New, Group. Add some users to that group by selecting those users and right-clicking, choose Add to a Group when the Select Groups wizard appears, type in the name of our security group and click on Check Names, click ok when done. you've now added some users to the Active Directory security group called Software Updates Management Report Readers. Step 4. Assign the Active Directory Security Group to our custom role Perform the following on your Configuration Manager 2012 server as SMSadmin. In the Administration pane, expand security and select Administrative Users. In the ribbon click on Add User or Group when the Add User or Group wizard appears select browse and search for our previously created Active Directory Security Group, type in Software Updates Management Report Readers and click ok next we need to assign this group with our custom role, so select Add to add security roles, scroll through the list of roles and select our custom role: SUM Reports Reader as per the screenshot below Click OK when done (leave the Assigned security scopes and collections as they are) Our active directory security group is now assigned the custom SUM Reports Reader security role. Step 5. Verify the custom role has the permissions we need Perform the following on your Configuration Manager 2012 server as a member of the Software Updates Management Report Readers active directory security group. We will now test our new custom role by starting the Configuration Manager console as a user which is a member of the previously created active directory security group. To do this right click on the Configuration Manager console icon in the system tray and hold down the shift key, then right click again (while holding down shift) on the new configuration manager console icon so that we can get a context based menu option called Run as Different User. when the security credentials window appears, type in the credentials of a domain user that you have previously added to the Software Updates Management Report Readers active directory security group, click ok when done. After a while, the Configuration Manager console will appear as it would if started by that user and you can immediatly see that it looks different, only the bits that are relevant to this user running Software Update reports are displayed in the console. When you add (or remove) permissions from the role, this view will change however you should close and re-open the console to see the new view with the credentials of your desired user. We have already defined our permissions so lets select Monitoring and expand Reporting and then select Reports. Notice how only 48 software update related reports appear (in comparison to the 445 or so reports that a member of the Full Administrator security role would be able to view). and below is what a Full Administrator would see in the same Reports pane The difference in the number and type of reports available and what you can do/see in the Configuration Manager console is governed by Role Based Administration, cool huh ?

if you exit diskpart can you dir c:\ ?

they must press F12 twice !, the first time gets the network ip address, contacts WDS, downloads some files, the second is to start network boot proper so that you can start your task sequences, so that user must press F12 when stated on screen, is your issue similar ?

you MUST press F12 for network boot when you see that message, have you tried that.... ?

Installation Part 1: how can I install SMS 2003 SP2? Part 2: how can I configure SMS 2003 ? Part 3: SMS 2003 final configuration Configuration how can I deploy an application using SMS ? how can I upgrade SMS 2003 to SCCM 2007

the collation must be as specified, have you tried reinstalling sql from scratch ? if it's a virtual machine should be easy to revert...

i mean, what does the actual application that you are trying to install, that MSI log file say, not the appenforce.log...

before you see this error what do you see on screen ?

here is a list of some of the System Center Operations Manager 2007 Guides I've put together. Installation Part 1. Create AD accounts Part 2. Install IIS and required role services Part 3. Install SQL Server 2005 sp3 Part 4. Install Operations Manager 2007 configuration Now that you have Setup Operations Manager 2007, you will need to configure it. Part 1. Configure Computers and Devices to Manage Part 2. Import Management Packs Part 3. Configure Reporting

what does the application installation LOG file tell you

c:\windows\debug\netsetup.log will cover domain join failures, look at that log file

i'll be covering migration soon in a new post, watch this space

hmm that shouldnt happen, can you take a screenshot/photo of what you are seeing please, and include diskpart info for me also (bring up a command prompt and run diskpart, select disk 0, list par

It is currently in the Site Properties of your site, under the Signing and Encryption tab, It was re-worded and now says: Require SHA-256.