gatorcb

We are trying to migrate from 2007 to 2012. Our collections won't migrate because we are using queries that reference a 3rd party product in 2007 that's not installed in 2012. Here's what we have select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemGroupName = "DOM\\APP-AdobeApproval" or SMS_R_System.ESDmemberof = "DOM\\APP-AdobeApproval" Since we have over 1000 collections and are still using ESD, we'd like to have a script return the above data to a file. Then we break that file up into smaller sections (by hand), then we have a script take that new smaller subset file as input and remove the "or SMS_R_System.ESDmemberof = "DOM\\APP-AdobeApproval"" part (basically the esd piece). Then we'll create a migration job in sccm 2012 and migrate those apps. Then we need another script to read the smaller subset file again and put the query back as listed above. Any help would be much appreciated. I don't do much with vbscript

I'm in the process of running through scenarios of migrating cm2007 objects to 2012 in a lab. To make things a bit more tricky I'm trying to leave off the default scope (use another). I'm seeing some weird issues I’ve noticed that if the admin acct used to create the migration job doesn’t have the “default” scope it doesn’t run the job and it skips several of the wizard windows. For instance it won’t show the package screen. My end goal is to have a scope for the workstation side and one for the server side, but allow the workstation side folks to migrate everything. I have successfully split out the workstation/server collections and updates functions already. Workstation Admins won't have access to all systems, but rather a workstation systems (to be used for limiting) collection. Note full admins would have access to all scopes. At this it seems my only option is to allow the default scope for now and make sure all the migrated objects have the workstation scope ticked during the migration job. Anybody run across this or figured out a similar plan? Thanks

Did you ever resolve this? We are experiencing the same issue

I have downloaded the bits today Mar 4th from both volume licensing and technet and both say sp1 beta after running splash->then clicking install. Is that a bug?

Thanks....I figured it out...you have to install wds first too before you add the pxe role

We installed a dp, setup a pxe point, configured multicast, adding both the x86 and x64 sccm boot images to the pxe share, added the boot and os images to the regular dp share, opened the firewall ports. What else are we missing? Is WDS required or just as a fallback? Thanks

Is it possible to integrate the application web portal into sharepoint? Basically is there a web part for it? Thanks