• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. rado
    3. Topics
    R
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 49
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by rado

    • R

      Sysrep win 7 join samba NT domain

      Windows Problems
      • • • rado
      8
      0
      Votes
      8
      Posts
      4.7k
      Views

      R

      Ok, sorry for delay, here is what we use to make win7 join Samba NT4 domain (maybe it helps somebody):

      after sysprep, fog automatically renames host (it’s done fairly early after sysprep, so there is little or perhaps no chance that computer will join domain with bad name), then it restarts and downloads associated snapin - I named it setup_complete_snapin - which contains 2 scripts:
      [LIST=1]
      []setupcomplete.cmd
      []join_domain.ps1 (powershell script)
      [/LIST]
      SETUPCOMPLETE.CMD:
      [CODE]
      @echo off

      rem delete unattend files
      del /Q /F c:\windows\system32\sysprep\unattend.xml
      del /Q /F c:\windows\panther\unattend.xml

      rem delete dir with additional drivers (those which win didn’t install automatically - needs registry update for win to look here)
      rd /S /Q c:\Drivers

      rem win activation
      cscript //b c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
      cscript //b C:\windows\system32\slmgr.vbs -ato

      rem office 2010 activation
      cscript “c:\Program Files\Microsoft Office\Office14\ospp.vbs” /act

      rem registry changes
      :: enable self deffense (registry protection) for NOD Endpoint Antivirus 5.0 - disabled before sysprep, because of sysprep crashes with this enabled
      REG ADD “HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Plugins\01000001\Profiles@My profile” /v selfdefense /t REG_DWORD /d 0x1 /f
      :: for win7 to join Samba NT4 domain
      REG ADD “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters” /v DomainCompatibilityMode /t REG_DWORD /d 0x1 /f
      REG ADD “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters” /v DNSNameResolutionRequired /t REG_DWORD /d 0x0 /f
      :: fixes problems with login (source: https://lists.samba.org/archive/samba/2010-October/158591.html)
      REG ADD “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters” /v DisablePasswordChange /t REG_DWORD /d 0x1 /f

      rem domain join
      :: didn’t work without cd
      cd \windows\temp\setup_complete_snapin
      powershell set-executionpolicy remotesigned
      powershell .\join_domain.ps1
      powershell set-executionpolicy allsigned

      rem extends partition to whole disk
      diskpart /s .\diskpart.txt

      :: sleep a la MS Windows 🙂
      ::ping -n 10 1.1.1.1

      rem restart
      shutdown -r -f -t 120

      Exit
      [/CODE]
      For domain join, really needed are only sections: domain join, registry changes (for win7 to join Samba NT4 domain) and perhaps restart.

      JOIN_DOMAIN.PS1:
      [CODE]

      user and pass - pass has to be in apostrophes, quotation marks didn’t work

      $User = “DOMAIN\USER”
      $Pass = ConvertTo-SecureString ‘PASSWORD’ -AsPlainText -Force

      create credentials

      $Credentials = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $User,$Pass

      join domain with loggin to file

      #add-computer -domain DOMAIN -credential $Credentials 2>&1 > join_domain.log

      join domain

      add-computer -domain DOMAIN -credential $Credentials
      [/CODE]

    • R

      "Successfully created tasks...", but erros in multicast.log

      FOG Problems
      • • • rado
      7
      0
      Votes
      7
      Posts
      2.4k
      Views

      R

      I started 1 task for whole group (around 80 clients) and it ended up with 4 (and second time with 5) tasks with the same number of udp-sender processes, logs etc. The tasks had variable number of clients (around 20 in average)…
      Last time it ended in a mess - made few tasks (I think 3 or 4) and then it couldn’t find clients or what:

      [CODE]
      [07-02-14 1:59:50 pm] | Task (20) cpu is new!
      [07-02-14 1:59:50 pm] | Task (20) /images/cpunew image file found.
      [07-02-14 1:59:50 pm] | Task (20) cpu failed to execute, no clients are included!
      [07-02-14 2:00:00 pm] | Task (15) cpu is already running PID 19255
      [07-02-14 2:00:00 pm] | Task (16) cpu is already running PID 19448
      [07-02-14 2:00:01 pm] | Task (17) cpu is already running PID 19639
      [07-02-14 2:00:01 pm] | Task (18) cpu is already running PID 19831
      [07-02-14 2:00:01 pm] | Task (19) cpu is already running PID 20015
      [07-02-14 2:00:01 pm] | Task (20) cpu is new!
      [07-02-14 2:00:01 pm] | Task (20) /images/cpunew image file found.
      [07-02-14 2:00:01 pm] | Task (20) 1 client(s) found.
      [07-02-14 2:00:01 pm] | Task (20) cpu sending on base port: 62908
      [07-02-14 2:00:01 pm] CMD: cat “/images/cpunew/d1p1.img”|/usr/local/sbin/udp-sender --min-receivers 1 --portbase 62908 --interface eth1.212 --full-duplex --ttl 32 --nokbd;cat “/images/cpunew/d1p2.img”|/usr/local/sbin/udp-sender --min-receivers 1 --portbase 62908 --interface eth1.212 --full-duplex --ttl 32 --nokbd;
      [07-02-14 2:00:01 pm] | Task (20) cpu has started.
      [/CODE]

      I don’t know what went wrong - I was testing change of multicast interface, so was changing interface, creating task, looking if it works, killing the task few times until this mess… then I just restarted server, because everything was too slow (which I observe since upgrade to 1.1.1, but I’m not sure if the problem is in FOG or my server)… strange things :)… maybe the creating and killing of tasks made a bit mess in the database or what…

      BTW: is this ok? (it’s from code excerpt above):

      [CODE]
      [07-02-14 2:00:00 pm] | Task (15) cpu is already running PID 19255
      [07-02-14 2:00:00 pm] | Task (16) cpu is already running PID 19448
      [07-02-14 2:00:01 pm] | Task (17) cpu is already running PID 19639
      [07-02-14 2:00:01 pm] | Task (18) cpu is already running PID 19831
      [07-02-14 2:00:01 pm] | Task (19) cpu is already running PID 20015
      [/CODE]

    • R

      FOG dashboard questions

      General
      • • • rado
      6
      0
      Votes
      6
      Posts
      2.5k
      Views

      R

      Hi, my colleague found this regarding 10 Mbit mode: h ttps://communities.intel.com/thread/11355?start=15&tstart=0

    • 1 / 1