Jump to content


67_dbc

Established Members
  • Content Count

    36
  • Joined

  • Last visited

  • Days Won

    1

67_dbc last won the day on August 9 2013

67_dbc had the most liked content!

Community Reputation

1 Neutral

About 67_dbc

  • Rank
    Advanced Member
  1. Niall, I know this is a year later response, just been really busy. Anyways, I've taken the USB Boot Media approach for my guys to get around this issue. The SCCM DP on the ESX host is using vmxnet3 NIC. We are on VMware ESXi 5.1.0. I've tried E1000 NIC but I did not see anything change. I've given MS 3-4 months to work on this and they keep telling me its the network but with several pcap logs, nowhere shows the break in communication during handshakes between Primary, the DP or the test VM Client. I've been given a diagram how PXE flows including pictures the network/sccm team drawn usin
  2. I am actively working on these Dell Wyse Thin Client WES 7 x32 using SCCM 2012 SP1 today as well. Its been a long journey getting these things to work properly and stable for the matter. Nonetheless getting support from Dell is nearly impossible to whom has experience with this and SCCM. Hoping perhaps if either of you spent time on these enough I could benefit this thread. Would either of you know or seen where these devices go into Service Locking Mode and only the Administrator can log on? I've done some research on it and pointed to possibly the clientstate.dat is the culprit matter b
  3. Update: We decided to open a case with MS and they can't seem to figure out why either as of yet. They been moving my SCCM environment all over the place trying to figure it out. From the community, nobody else has had this issue before?? Anyone? Eric
  4. Thanks for the reply. The Client is on the same subnet as the ESX host as the SCCM server. There is only one router between the host and the client. The Cisco router itself is doing the DHCP handoff. PXE/WDS reside on the same box. The WDS role was setup then left alone as is. I've compared those settings to be sure from a working PXE to this troubled one and didn't find any differences. The WDS setting related admin approval is not checked, so I have to rule that out. Any other thoughts? Thanks, Eric
  5. Hi, I've been experiencing an issue where my PXE Boot client is unable to contact the server. The strange thing is that, the Contacting Server step could be 20 minutes or up to an hour trying to attempt. There has been cases where I will sit there and watch it and it will eventually locate the BootImage and allow me to hit F12 to start the TS. Now, PXE is configured in SCCM the same way on my other 30+ DPs and I have 2 that have this same behavior. Please see attached problem. I've removed the PXE option from the DP, I've removed WDS, rebooted the server, re-set everything back up
  6. Just to share, if helps any.... Here is the same machine with an uninstall and re-install of the client. CHRNOO-WT-T430 Running query 'SELECT * FROM CCM_Service_HostedApplication WHERE Type="Server"' against namespace: '\\CHRNOO-WT-T430\ROOT\CCM\Policy\Machine' 5/12/2014 12:45:00 PM 1212 (0x04BC) CCMExec is currently NOT hosting a server application. 5/12/2014 12:45:00 PM 1212 (0x04BC) Machine: CHRNOO-WT-T430 5/12/2014 12:45:00 PM 1212 (0x04BC) OS Version: 6.1 Service Pack 1 5/12/2014 12:45:00 PM 1212 (0x04BC) SCCM Client Version: 5.00.7711.0000 5/12/2014 12:45:0
  7. PolicyAgent.log on CHRNOO-WT-T430 I don't see anything wrong. Requesting Machine policy assignments 5/12/2014 9:33:11 AM 7132 (0x1BDC) Requesting Machine policy from authority 'SMS:002' 5/12/2014 9:33:11 AM 7132 (0x1BDC) Raising event: instance of CCM_PolicyAgent_AssignmentsRequested { AuthorityName = "SMS:002"; ClientID = "GUID:ba439da0-d47c-453f-813e-7eff5d77209f"; DateTime = "20140512143311.695000+000"; ProcessID = 3744; ResourceName = "CHRNOO-WT-T430"; ResourceType = "Machine"; ThreadID = 7132; }; 5/12/2014 9:33:11 AM 7132 (0x1BDC)
  8. Resolved this by clicking each and every one container, unchecking the Enable ADSD option, then enable ADSD and add the containers all over again.... Must be a bug. Eric
  9. I've been dealing with about 400 machines out of 1500 that report that the client in the console shows No. I've gone to several clients only to find that they do have it installed, listed in Control Panel, MP registration is valid and assigned to the one and only Site on our Domain. This occurs on multiple subnets not just 1 and I have several machines in different subnets that do report with Yes Client. SO here I am trying to locate the disconnect... Machines on different subnets, each have a valid boundary and boundary group assigned to a DP, with the check box on Site Assignment of my s
  10. I swore I wrote a post on this but I can't find myself where it was posted... Anyways, I am trying to remove an AD Container within the Active Directory System Discovery Properties. I am getting the following message when I try to remove it. I've gone to the point of stopping SMS_Discovery services to ensure that its not running while I am trying to remove this old OU entry from ADSD. Reason for removal of course is the fact the container doesn't exist in AD any longer. So my logs are filling up during the discovery interval and reports that the OU doesn't exist. With any attempt, I am getting
  11. Figured this all out. You are to be putting the OS on the HDD so it needs to be disk 0 and according to Lenovo, you need to install ExpressCache to get the SSD functionality of it. Its almost transparent, therefore, you install it and doesn't require any additional configurations. Problem is they can't me what tools are available verify that its truly is working but I suppose you can benchmark before and after the software install. http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS035460 Silent install switch is not available in the README. IF you need it, please use /s /v
  12. I have a silly question...How do you remove an entry that was added manually in the AD System Discovery Properties? Note: The following AD container doesn't exist any longer, which is the reason for me to remove it from AD system discovery altogether. I am getting the following error when I attempt this. Am I suppose to stop any services prior to removal? Perhaps, do I need to go to my AD side and re-add that OU just so I can remove it from SCCM ADSD??? I prefer not to because that will cause havoc internally with our server group. Anyone else dealt with this before? SCCM 2012 (no CU o
  13. Can someone assist in details on the formatting? I am trying to install OSD via SCCM 2012 on Lenovo X240 series. Currently the configuration hardware is 16GB mSATA and 7200RPM 500GB HDD. I guess what I don't understand is, am I suppose to load the OS on the mSATA, which to me seems logical? The additional drive, how is that being used for additional storage space? From the original poster jhille, I did exactly what was done but my results don't add up as expected. Someone have additional screen shots from Disk Management or TS Volume Properties are suppose to look like? Thanks, Eri
  14. 67_dbc

    MDOP MBAM

    Appreciate the quick response Jorgen. Can you elaborate more on the GPO to force encryption? If you mean, do I have MBAM MDOP GPO configured with services/reporting then yes, I do. My only issue is suppressing that Client UI box, what area of focus am I needing to look at suppressing it so users are not required to click on anything? I just want to silently encrypt drives without user interact. Through SCCM, I am using the UDI Wizard using ZTIBde.wsf from the UDI Wizard, so I am not sure what to use to apply that outside of SCCM via logon script or SCCM deployment, have examples perhap
×
×
  • Create New...