Jump to content


johnli

Established Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by johnli

  1. Hi!

     

    I'm using a VBS script during OS deployment to set the AD computer description.

    But results are unpredictable at best (if you use numbers or gaps)

    Does someone has a suggestion for a good working solution ?

     

    script that I was testing :

     

    cscript.exe adcompdesc.vbs “%ComputerDescription%”

    dim Computerdn, strComputerName
    dim Args
    
    
    Set WshShell = WScript.CreateObject("WScript.Shell")
    '----Get Computer DN------
    Set objADSysInfo = CreateObject("ADSystemInfo")
    ComputerDN = objADSysInfo.ComputerName
    strcomputerdn = "LDAP://" & computerDN
    Set objADSysInfo = Nothing
    '-----Read commandline---
    Set args = WScript.Arguments
    
    
    strdesc = args(0)
    Addcompdesc strdesc
    
    
    Function addcompdesc(strPCdescription)
    
    
    Set objComputer = GetObject (strComputerDN)
    objComputer.Put "Description", strPCdescription  
    objComputer.SetInfo
    end function

     

  2. Hi!

     

    Need some help, stuck witch this issue.

     

    ISSUE : After I hit F12, the client downloads the .wim from the correct server.

    But when the image is downloaded, it take very long (5min) to come at the Task Sequence Wizard

     

    When I check the smsts.log, then I see that the client want's to connect to a DP in a non-trusted domain.
    That server is not available, and after a few tries the client is going for the appropriate DP.

     

    The client is in the correct boundarie, en IP Helper refers to the correct server.

     

    post-31283-0-64076800-1466160462.jpg

     

    Any tips, suggestions ?

    post-31283-0-64076800-1466160462.jpg

  3. this is what I use for my subnet based collections.

     

    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.IPSubnets in ("10.0.1.0") and SMS_R_System.OperatingSystemNameandVersion like "%workstation%"

     

    I must test this....thanks !

  4. Hi!

     

    How can i build a query based on a IP sunnet ?

     

    Address: 159.171.10.1
    Netmask: 255.255.255.128 = 25

    Network: 159.171.10.0/25
    Broadcast: 159.171.10.127
    HostMin: 159.171.10.1

    HostMax: 159.171.10.126

     

    I have now (but it won't do the job) :

    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_NETWORK_ADAPTER_CONFIGURATION on SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.ResourceId = SMS_R_System.ResourceId where SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.IPAddress >= "159.171.10.1" and SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.IPAddress <= "159.171.10.126"
    

    Any tips, ideas ??

  5. I've found that when deploying new sequences they can take a while to become available as even when selecting "As soon as possible" during the sequence deployment, it then defaults to at a specific time (which is usually the current time) and the "Soon as possible" option becomes greyed out. It seems that the boot image uses a different time zone that is sometime in the future to my SCCM server.


    My general way around it is, after creating the task sequence and deploying it, go into the properties of the deployment and then the scheduling tab, then change the date to some time in the past. If you try to do this during the deployment it wont go more than 1 minute in the past, but in the deployment properties it can be any time.


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.