Jump to content


Irfansj

Established Members
  • Posts

    9
  • Joined

  • Last visited

Irfansj's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks RocketMan, Yes you are absolutely right. The registry also got executed but it got executed in HKLM--> software --> WOW6432 node --> Microsoft --> windows --> ..... instead of HKLM --> software --> Microsoft. Thanks for your help. If i am able to resolve this , i will definately update you.. Thanks once again for your great support. Regards
  2. Hi Rocket Man, Updates: I was able to copy the 2 Dll files. However it didnot get copied to c:\windows\system32. It copied to C:\Windows\SysWoW64 . I am running hardware x64 with win7 x64 editions. The registry also didnot execute.
  3. Step3: Correction I create a package Package --> Create Package --> The package contains source files (pointed to the \\sccmsrv\software\dll\ ) folder. Select "Create a Standard Program"
  4. Hello Rocket Man, Not sure, if i have understood correctly, requesting to confirm steps below. Step1. I created a batch file : DLL.bat (with exactly the same contents as below) @Ehco copy %~dp0passwordreset.dll "c:\windows\system32" copy %~dp0msvcrt100.dll "c:\windows\system32" regedit.exe /s regkeys.reg @Exit My doubt in step1. Doubt1 should i use the commandline regedit.exe /s regkeys.reg in the batch file OR I need to replace with my actual registry files as below regedit.exe /s unregister.reg regedit.exe /s unregister.reg Doubt2 should i use the inverted commas as "c:\windows\system32" OR c:\windows\system32 Step2: I copied this batch file, passwordreset.dll, msvcrt100.dll , unregister.reg and register.reg inside \\sccmsrv\software\dll folder. The software folder is shared for everyone Step3: I create a package using below steps Package --> create package --> The package contains source files (pointed to the \\sccmsrv\software\dll\ ) folder. Selected "Do not create a Program". This only created a package. Step4 I then distributed it to DP's via "Distribute Content" Step5 I than apply to collections. Regards Irfan
  5. Hello, I have struggling hard to create a simple package using a batch file. Probably if some one can help I need to copy DLL file to c:\windows\system32 directory on all managed clients. Also I need to run .reg file on all client workstations which will create keys in the registry. Action I took: I created a batch file using copy \\ServerName\.... c:\windows\system32 regedit /S \\Servername\path\register.reg I than go up and create a standard program from the Package --> New Package wizard. However i am unable to copy these files to system32 directory. Is there a different way to create such packages?? Where should i search for error logs on client side ??
  6. Hello, I have struggling hard to create a simple package using a batch file. Probably if some one can help I need to copy DLL file to c:\windows\system32 directory on all managed clients. Also I need to run .reg file on all client workstations which will create keys in the registry. Action I took: I created a batch file using copy \\ServerName\.... c:\windows\system32 regedit /S \\Servername\path\register.reg I than go up and create a standard program from the Package --> New Package wizard. However i am unable to copy these files to system32 directory. Is there a different way to create such packages?? Where should i search for error logs on client side ??
  7. Hi Peter, Thanks very much. I looked the cas.log file and was able to find out the source DP. Thanks verrrrryyy much.
  8. Apologies Peter, Looking at this reply today only. I will look in the CAS.log and find out. If you know particularly what needs to be checked in the cas.log, it will make my life easier.
  9. Hi, I have SCCM 2012 environment with multiple DP's. I need to identify which DP is used for deploying packages to the clients. Can we get this information in reports or any log files? This will ensure that correct DP is being used for the entire collections. Regards
×
×
  • 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.