Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

  • Days Won


jkirshy last won the day on September 4 2013

jkirshy had the most liked content!

About jkirshy

  • Birthday 04/23/1964

Profile Information

  • Gender
  • Location
    Houston, Texas

jkirshy's Achievements


Newbie (1/14)



  1. SetupClient.exe /q /targetdir "c:\program files\Microsoft CRM" INSTALLLEVEL=2 /l c:\crm_client_setup_log.txtlook at this web site, its great...http://www.itninja.com/software/microsoft/dynamics-crm-2011-client/5-2606 deploy as a .exe
  2. Stop using UEFI boot, or update your boot image to include the updated stuff for uefi.
  3. Pxe booting depends a lot on the nic card in that pc. Update the bios of the pc's in question. If these are older computers put in a new nic or go to bios and make sure all options for nic card are correct, pxe ability, turned on etc. One last thing have your network guys make sure portfast is set on all of you switches. Your pic above shows clearly the pc is not contacting the wds service on the sccm server, due to too much activity or simply times out. Make sure in your registry of the sccm server find wds settings and double the packet size, you can Google that and find the exact key to adjust. Finally check your network card on your pc, is it optimized, have correct dns, ping and do you get good reaction times, does dns work by name and by ip, can you do nslookup by both also. Do you have dns set up correctly on all of your dns servers, you need an entry for you sccm server.
  4. If you rename the pc, the mac is the same so eventually it will change in sccm to the new name. I've done it both ways. I just get tired of looking at all the dell minint-bla bla bla computer names until it goes away in sccm.
  5. You have 2 issues. I would load a new sccm on new domain, you can import software packages etc. The process of capture profiles on such a big scale , im have not seen anything like that. Im sure if you asked this question on a domain admins site there is an answer.
  6. Simple as above hit f8 if you have enabled tools in pxe and do an ipconfig. IF you get an address your network card on your boot image is good, and the problem is software task related. More than likely you will have no ip address.. Go to dell get the latest nic driver from dell, import it into your boot image. warning sometimes dell renames drivers, go to manufacture site and get driver for network card. once you load that missing driver, redeploy. then pxe boot success. I had the same problem and banged my head against the wall, even dell was telling me I had the right nic driver for dell 5610, however I googled that driver and found the one from the manufacture and it worked. I celebrated for days! Advice to anyone, on any new dell, download there cab files, import them into sccm, then user a windows 7 image or 8 and create a Software task sequence to combine the two. Capturing and deploying is a pain.
  7. You really ask a difficult question to answer. First have you checked the logs on the client pc to find out why they failed, did you put a pre-requisite in your software deployment. Do you have any widows firewall issues by group policy or local, does your sccm acct have proper access. Sccm troubleshooting is log based. Use the log viewer that comes with Sccm. Are your pc's in the same v-lan or separated by hardware firewall rules. Certain ports have to be open , file and print sharing etc on the domain controller by GP. Check the account your running the software distribution as, or change it to troubleshoot. Check your logs on the server. Have you installed right click tools to help you troubleshot remotely. Connect to the client pcs, just because you get a software failed notice , does not necessarily mean the software actually did not get installed. As far as grouping can you group by logical name, location, ip range, Or group using a variable query statmemnt for example, here is one, im sure I got it here. I love this website. 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 inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like "%Adobe of course change adobe for your software or lack of. This is just a starting point, look at your deployment see if your group you are deploying too actually shows each member, are they physically turned on.. Initiate a application cycle or machine policy on the whole group. so all pcs will get the latest advertisement. LOGS< LOGS LOGS> good luck.
  8. Looks like your laptop drive is encrypted with bit locker. Your process might be slowed down by that. Make sure you format your drive with a 350 mb partition than the rest is for your c drive. For faster pxe speed, update your bios, change the packet size in your server registry for your WDS. ( google search for this one) It works great. You need to add a task sequence ( set task sequence Variable ) variable OSDPreserveDriveLetter False, to use the C drive. Make sure your connection to your windows iso or media is on your sccm server in your setup. In config mgr, turn on Pxe with tools. This way you can hit f8 at any time open up Log viewer and open up log file to see what is happening real time.
  9. Pxe boot on Dell or any other manufacture. After all issues above are fixed. The next step is to find the manufacture of the network card, then use there drivers to inject into boot image. For dell there driver packages are renamed. For example the Intel 1217-LM driver is really the Intel Pro 1000 and uses a different inf file. This is very important. Also, don't put the Dell cab files in the task sequence, you will get some random storage errors upon task sequence completion.
  10. Problem solved, turns out if you install windows 8.1 ADK, it will prevent you from restoring the boot images, no matter how you create them. My mistake was trying to uefi boot and reading some other blog that said install windows ADK 8.1 and you can then uefi boot. He should have said, update Sccm sp1 to R2 version and then you can work with uefi bios type of computers. http://deploymywindows.blogspot.com/2013/07/sccm-2012-sp1-specified-unc-path-does.html?showComment=1392048241859#c1118562768097924795 this is the article that helped me. Don't use adk 8..1 if your only on the sp1 version of Sccm 2012. Thanks all for helping.
  11. Help, Im having the same issue, The boot images are gone I've followed all the above workarounds to recreate them. Question... I use the boot wizard in Sccm to add a boot image, I use the wim image that was created by the deployment and imaging tools, I browse to the wim image (boot.wim) but the second drop down box does not populate. Its like im not using the correct sources folder to pull the original boot file? Is the boot.wim originally come off of the windows 7 cd, or from the Sccm cd? If so is it from the sources folder. I think I use the boot.wim? I tried to recreated the DP point but it does not recreate the boot images? Probably because it sees the file structure already in place so the boot images don't get recreated. This all started because we have a bunch of new dells coming in that uefi boot and we cant get them to pxe boot, because of lack of network drivers. What a nightmare. Legacy or UEFI boot wont start up. Dell 9020. The next option is to go to r2 but im not sure if that will re-create the boot images. There has to be an easy answer??
  12. I need some advice? How do most of you reconcile the device lists? I have 2393 in my all devices list, but only 1637.00 in all desktop and server clients. Ive massaged all the discover settings but want to make sure I have the optimum settings to pick up all devices that are under 60 days old. I put a new device on the network and the sccm client and mandatory software installs in under 15 minutes. I have some devices that are excluded from discovery, so they should not be in that list. I set the discover limit to only capture stuff from AD that has logged in to ad within the last 60 days. I Im preety sure my numbers are correct but my boss thinks im about 200 devices off. The list of devices changes constantly obviousoly. How can I reconcile the difference in number of devices in the default list of " All Systems" and "All Desktop and Service Clients" ? How do you make sure you are getting all the devices on your network.?
  13. This topic should be closed. This issue was fixed by uninstalling Application web service point and website point. I blew away any remnants of IIS and reinstalled and then in sccm added the two roles and all is well.
  14. What about the firewall policy on the client? By default we turn off the domain firewall on all pc's, probably not it but make sure its off, and the service off. Verify no other firewalls are running. Next I would check the permission on your site code folder on the server itself. Next, make sure your AD system container in system management entry for your sms_MP-site code, has the right permissions. Your sccm server should have full permission I have mine as sccm2012$. Watch ccm client log on your clients for errors, this is your key. Download client action tools. this standalone tool will give you all kinds of things to check on a client, wmi, firewall, policy's, repair, sccm client, client health tools. Oh and download latest right click tools they really give you a lot of tools to connect to the client! This is what is supposed to happen, To start the process, initiate machine policy retrieval and evaluation. This is the next process not sure where I got it from but most likely this web site. Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process: 1.Client location services identify the site code and the MP it is supposed to connect to. 2.The client connects to the Management Point and downloads the policies. 3.Once the policies are downloaded it sends the heartbeat record to the server. 4.Once the server receives this heartbeat record these are converted in to DDR and processed. This will set the client flag to 1 which will make the client status display as Yes in the console. 5.On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to No. So only if this process is completed and it continues to happen will the client remain reporting to the server. This is why I said earlier that client management is a continuous task. If this does not work, delete all ccm files on client c drive and re-install and watch log on client machine using cmtrace.exe a log trace tool.
  • Create New...