Jump to content


tmiller_hockey

Established Members
  • Posts

    139
  • Joined

  • Last visited

Everything posted by tmiller_hockey

  1. I am in the same boat. No things displayed in Inventoried Software under Asset Intelligence.
  2. Bump... Anyone have an idea to find out this information or if it is even in the DB?
  3. All of a sudden (last month I didn't have this problem) I get an error when trying to update some deployment packages or even create new ones for Windows 7 update deployment. I run though all the steps and when I get to the end (See Attachment). Anyone have an idea? I've checked permissions on the folder where the updates reside.
  4. So you've had no issues when deleting them?
  5. I was looking for an easy way to obtain the following information about a computer. Last login date/time and who the user was that logged in. User affinity is setup but it isn't populated with the true information. See screenshot. The reason we need this information is students come in and tell our technicians they've lost their laptop or it was stolen. This info will give us some info that could be of help. Thanks
  6. I do have MDT Installed but for right now I'm sticking with my vbs script as when our machines are imaged, they usually know what structure for naming to use. We use this for a naming scheme: APPENDING ABBREVIATION-SERIAL-TYPE OF MACHINE (Student Or Teacher) Would look something like this. SGP-L3RV323-T The script I use now pops up an inputbox that asks for the Appending and the machine type and automatically pulls the serial. I know this can be done in MDT using an HTA but have no clue how to do it.
  7. That's what my thought would be, you have to define remote tools users in the client settings.
  8. Also found out the hard way that if you try to look in the folder to view those files, it asks for administrator permission. WDS service ended up in error after this. In my case when I clicked OK, it wiped out all the security on that folder and replaced it with my domain admin account as full control. Had to go back in and give the System account permissions and my WDS started working again.
  9. Currently there are over 166,000 files in that folder on my PXE DP. Seems kind of crazy to me for that to be the way it is.
  10. I have an idea but wanted to see if anyone else knows why this happens. I think it is possibly due to basic authentication being enabled in IIS for that particular site. I could be wrong though Ideas?
  11. Thanks, This works and now I have to tailor it down to version numbers to differentiate between 2005 and 2008. Would be alot easier if Microsoft just put that in Add/Remove programs or just made it part of the Product name instead of "Microsoft SQL Server"
  12. Found a solution to this on the ConfigManager Forums on Microsoft's site. 1. Install BITS 2.5 manually (requires restart) 2. Install Certificate Hotfix KB968730 (requires restart) After these are installed, ccmsetup.exe will appear in task manager and everything will install fine.
  13. Seems that the client will install on our 2008 servers but not on our 2003 boxes. They're all in the same ip range, covered under the same boundary/group. Is there something I'm missing with this?
  14. Does anyone have a clue on a query that would return machines with any Version of SQL Server installed? I'm trying to create a collection of SQL machines. Thanks!!
  15. This is what I use in my TS right after partitioning. ' vbscript ' Declare Variables Dim strCampus Dim strSerialNum Dim strAppend Dim strComputerName Dim strLclUser Dim strLclPW Dim strComputer Dim objWMIService Dim objComputer ' Set Variables SET env = CreateObject("Microsoft.SMS.TSEnvironment") strLclUser = "Administrator" strLclPW = "adminpassword" 'Prompt For Campus strCampus = INPUTBOX("Enter Campus Name") 'Prompt For Teacher Or Student strAppend = INPUTBOX("Enter Teacher Or Student") ' Obtain Serial Number strComputer = "." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colSMBIOS = objWMIService.ExecQuery("Select * from Win32_BIOS") For Each objSMBIOS in colSMBIOS strSerialNum = objSMBIOS.SerialNumber Next ' Set Computer Name strComputerName = strCampus & "-" & strSerialNum & "-" & strAppend 'Set OSD Computer Name Variable env("OSDComputerName") = strComputerName 'End Script
  16. Well I found the log on the external drive. Here is the relevant portion. The kicker is that I'm capturing to a 500GB Drive from an 80Gb drive... <![LOG[The execution of the group (Capture the Reference Machine) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="11:34:28.121+480" date="08-23-2012" component="TSManager" context="" type="3" thread="1760" file="instruction.cxx:2425"> <![LOG[Failed to run the last action: Capture the Reference Machine. Execution of task sequence failed. There is not enough space on the disk. (Error: 80070070; Source: Windows)]LOG]!><time="11:34:28.121+480" date="08-23-2012" component="TSManager" context="" type="3" thread="1760" file="engine.cxx:214"> <![LOG[Do not send status message in full media case]LOG]!><time="11:34:28.121+480" date="08-23-2012" component="TSManager" context="" type="1" thread="1760" file="utils.cpp:4736">
  17. Well that's great, machine rebooted and can't get the log now. I'm pretty much at wits end with trying to capture this image.
  18. Unfortunately yes it was on physical hardware as I wasn't the one setting it up and capturing it. I only got stuck with it after they couldn't get it to work. This image contains a huge huge amount of applications, ones we don't want to deploy over the network or are insanely hard to setup for silent installs including AutoCad, Autodesk Inventor, Adobe CS5, etc. To reinstall all this in a VM would take forever and would like to just capture what I have. Now I am receiving an 0x80070070 error, I'm trying to capture to an external hard disk. I'll post the smsts
  19. Peter that's what I was thinking. I'm assuming it is an error on the client's drive not the capture location I'm writing to.
  20. You can add your applications to the machine and then from the console create a "Capture Media Disk" you can then utilize it to capture your finished machine.
  21. Yes they are separate installs, Professional Plus doesn't include them.
  22. I've been trying to capture a machine and have had no luck with this one. It gets almost done with the capturing of the volume then gives me an error. Here is the relevant part of smsts.log <![LOG[Capturing D:\, volume 2 of 2]LOG]!><time="11:33:55.210+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="capturesystemimage.cpp:746"> <![LOG[Capturing volume D:]LOG]!><time="11:33:55.210+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimfile.cpp:437"> <![LOG[ Skipping \hiberfil.sys]LOG]!><time="11:35:42.413+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimstate.cpp:475"> <![LOG[ Skipping \pagefile.sys]LOG]!><time="11:35:44.862+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimstate.cpp:475"> <![LOG[ Skipping \SMSTSLog]LOG]!><time="11:45:46.539+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimstate.cpp:475"> <![LOG[ Skipping \System Volume Information]LOG]!><time="11:45:54.854+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimstate.cpp:475"> <![LOG[ Skipping \Windows\CSC]LOG]!><time="11:47:07.362+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimstate.cpp:475"> <![LOG[ Skipping D:\_SMSTaskSequence]LOG]!><time="11:53:07.114+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimstate.cpp:468"> <![LOG[WIM has entered capture phase for 215349 items]LOG]!><time="11:53:07.114+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimstate.cpp:385"> <![LOG[WIM error:D:\Windows\Installer\1453ed58.msi. Data error (cyclic redundancy check). (Error: 80070017; Source: Windows)]LOG]!><time="13:35:18.522+480" date="08-20-2012" component="CaptureSystemImage" context="" type="3" thread="1900" file="wimstate.cpp:193"> <![LOG[hVolumeImage = WIMCaptureImage( m_hImageFile, const_cast<LPWSTR>(pathTargetVolume.c_str()), WIM_FLAG_VERIFY ), HRESULT=80070017 (e:\nts_sccm_release\sms\framework\tscore\wimfile.cpp,475)]LOG]!><time="13:35:22.766+480" date="08-20-2012" component="CaptureSystemImage" context="" type="0" thread="1900" file="wimfile.cpp:475"> <![LOG[unable to capture the volume image (0x80070017)]LOG]!><time="13:35:22.766+480" date="08-20-2012" component="CaptureSystemImage" context="" type="3" thread="1900" file="wimfile.cpp:475"> <![LOG[imageFile.CaptureVolumeImage( (*itr), &saFilesToNotCapture), HRESULT=80070017 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,747)]LOG]!><time="13:35:22.766+480" date="08-20-2012" component="CaptureSystemImage" context="" type="0" thread="1900" file="capturesystemimage.cpp:747"> <![LOG[CaptureSystemImage( progressUi, slVolumesToCapture, sOfflineSystemRoot, ImageFile), HRESULT=80070017 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,908)]LOG]!><time="13:35:22.766+480" date="08-20-2012" component="CaptureSystemImage" context="" type="0" thread="1900" file="capturesystemimage.cpp:908"> <![LOG[Failed to capture system image. Data error (cyclic redundancy check). (Error: 80070017; Source: Windows)]LOG]!><time="13:35:22.766+480" date="08-20-2012" component="CaptureSystemImage" context="" type="3" thread="1900" file="capturesystemimage.cpp:908"> <![LOG[Closing image file \\tech-sccmdist-1\sources\project.wim]LOG]!><time="13:35:22.766+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="wimfile.cpp:358"> <![LOG[Command line for extension .EXE is "%1" %*]LOG]!><time="13:35:23.967+480" date="08-20-2012" component="CaptureSystemImage" context="" type="0" thread="1900" file="commandline.cpp:228"> <![LOG[set command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/enable:D:\Windows\system32" /version:6.1]LOG]!><time="13:35:23.967+480" date="08-20-2012" component="CaptureSystemImage" context="" type="0" thread="1900" file="commandline.cpp:705"> <![LOG[Executing command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/enable:D:\Windows\system32" /version:6.1]LOG]!><time="13:35:23.967+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="commandline.cpp:801"> <![LOG[Enabling OSD setup hook]LOG]!><time="13:35:24.060+480" date="08-20-2012" component="OSDSetupHook" context="" type="1" thread="980" file="osdsetuphook.cpp:317"> <![LOG[Process completed with exit code 0]LOG]!><time="13:35:24.076+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="commandline.cpp:1098"> <![LOG[Cleaning up partial image file \\tech-sccmdist-1\sources\project.wim...]LOG]!><time="13:35:24.076+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="capturesystemimage.cpp:932"> <![LOG[Finished with error code 0x80070017]LOG]!><time="13:35:24.996+480" date="08-20-2012" component="CaptureSystemImage" context="" type="1" thread="1900" file="capturesystemimage.cpp:942"> <![LOG[Process completed with exit code 2147942423]LOG]!><time="13:35:25.043+480" date="08-20-2012" component="TSManager" context="" type="1" thread="1836" file="commandline.cpp:1098"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:35:25.059+480" date="08-20-2012" component="TSManager" context="" type="1" thread="1836" file="instruction.cxx:3011"> <![LOG[Failed to run the action: Capture the Reference Machine. If anyone has an idea I'd love to hear it as this image is for a specific lab that has a huge amount of apps that are very large (AutoCad, Adobe CS5, and some more robotic 3d renderers) that we need to put on about 20 lab machines. Thanks
×
×
  • 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.