burnzdog

Hi All, Hope this is the right place to post this. Im picking up some SCCM work but its been a while since have been near a SCCM setup, so please bear with me. I have an issue where after deploying an application I have realised the boundaries groups may not be up to date or setup correctly. The problem I have is that if a machine is using an IP address that is not configured as a boundary, it will not connect to a DP. What I need - because hundreds of IP address ranges we have - is some kind of fallback rule that if the client falls outside of the boundary address groups that it will default to the default site. At the moment this isnt happening. I thought this was what the default-site-boundary-group did? but this group is greyed out and has no group members, and apparently this is default?

Thanks, both MSI were already downloaded just the program wasnt configured to use 32bit as well. It has worked now jsut took longer than anticipated. How often should a client check for changes?

SCCM2012R2. Limited experience. I have created a package and deployed. It has been successfully deployed to all DP's its a simple MSI file. When I created the package I captured both x86 and x64, however when I deployed I pointed the install at x64.msi thinking that will be sufficient but apparently there are 32 bit machines. So, I have now gone back into properties of my application and have added another deployment type and created the X64 variant. I then added requirements and associated each of the install with its O/S architecture. I am now expecting this to go out to the 32bit O/S's but noting appears to be happening? As both MSI files were in the original package I didnt think I will need to update push out this change>?Probably something obvious im not doing....help appreciated.

Hello all, Trying to use the latest IAK tools to create a unattend.xml file. When I try and open the WIM file for windows 10 I get an error. Catalog creation failed to complete. This 64-bit version of Windows SIM can only create catalogs for 64-bit Windows images. Anyone else had this issue?

Hi All, Trying to creat a build and capture for Windows 10 x64 on a VM. It seems to deploy the O/S OK but after rebooting it sticks on Installation progress: Setup Windows and Configuration MGR. I cannot open the smsts.log from C:\_SMSTaskSequence\logs\smstslog\ as it says its already in use. The build doesnt fail, its just stuck. Seems to be trying to do something in the background. If I ALT_TAB I can see the is a process running call FIRSTUXWND Any Ideas? Much appreciated.

Also is it standard to have to update the build images with NIC drivers before it will work?

Well that was going to be my later question. its since I have administered SCCM. Im using guide but Im trying to do this with windows 10. Im assuming the process is the same? Ive gotten a little further. I may have jumped the gun a bit and tried to PXE bot before I had created a Task sequence. Now that I have done that It has booted up. (not sure this is correct?) but whilst typing its failed Using HP laptops. Best to capture VM , yes? What is the best build process: Build a windows 10 with all base applications on Capture Deploy with task sequence to install extra apps. Repeat capture process periodically?

Hi all, Followed your guide for build and capture windows https://www.windows-noob.com/forums/topic/6353-using-system-center-2012-configuration-manager-part-7-build-and-capture-windows-7-x64-sp1/ However, Ive fallen at the first hurdle. Got as far as distributing the images, enabling PXE and updating distribution points. When I try and PXE I get error Network not found. Please check your network connection and try again. PXE log shows last entry: PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 4/20/2016 3:32:34 PM 644 (0x0284) Any ideas as im banging my head against the wall. Thanks

in case anyone's interested in this - failing to connect when trying run task was down to a .net 4 update. We uninstalled KB2840628 and worked again.... http://blogs.technet.com/b/configmgrteam/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configmgr.aspx

Hi all, Just had our SCCM 2007 migrated over to 2012. Ive just realised that all our drivers are looking at the 2007 config server for all driver paths. We have many drivers. Is there a tool we can use to change these locations? thanks Matt

Anyone?

I have just created a new task that i just the O/S install. Heres the log smsts.log

ESC00042.2 is in the SMSPKGSIG folder.

Password verified. Can ping management point from client. All packages and O/S have distributed to DP's

Any help would be appreciated.