Jump to content


DizzleSizzle

Established Members
  • Posts

    49
  • Joined

  • Last visited

Everything posted by DizzleSizzle

  1. How do i target a different os for a task sequence advertisement? I never get the screen as i do when i deploy software which ask me "what os can this program run on". am i missing something? Nevermind, your link solved my problem and down the road issues. great post!
  2. Yeah i tried multiple different attempts with the MSI from definition, just the regular MSIEXEC install with different flags...but every time i use the MSI it never finishes. Just sits there and continues to say installing, you then have to power off the machine. when i use the custom EXE from the SEPM i see it display to install on the task sequence display but it shows for like 2 sec (as it thought it installed successfully in 2 sec) then goes to the next task. doesn't error out and doesn't install anything.
  3. Hello All, In need of some help...I am in the process of deploying Windows 7 via SCCM OSD. Everything works great image comes down without issues, installs the SCCM client without issue ect..but i also have one software package install as the final step of the TS which is Symantec Endpoint Protection. I tried using the self contained exe file that has everything loaded within for server location and predefined policies...but the TS displays as it is going to install but just skips over with no error at all. nothing ever gets installed. I then tried using the msi rather then the loaded exe, well this time it runs the MSI but never finishes....anyone have any advice for this?
  4. thanks for the help, i went the easy route first and just renamed the PXEBOOT and BOOT folder in windows\temp folder to .old. added both x86 and x64 bootPE's back to PXE DP and finally WDS extracted the bootstrap files from them. PXE back and working. I am still having issues though trying to figure out how to assign a task sequence to only PXE. I tried finding how to advertise a TS only to Windows 2000 machines since i don't have any of them within my environment but no luck..
  5. Well today i noticed one of my other Admins had added a operating system image within the smspxeimages$ share. Now my WDS is not properly functioning...both the x86 and x64 SMS\boot folders are empty. I have re-started the WDS service and nothing. Seems like it can't extract the bootstrap files from the bootPE images i have added to the PXE DP. I tried removing the BootPE's from the PXEDP and re-adding them and still no luck. i restarted WDS again and still the folders are empty. I tried adding the files in from the same SCCM SP2 R2 server in my test lab which got me further in the PXE. Rather then saying no boot file it brought me all the way to the f12 portion then got some funky error about BCD could determine the OS. Is there anyway to get the WDS service back to normal, being that it will extract the bootstrap files from the BootPE in the smspxeimages share and populate back to the sms\boot folder.
  6. Hello, I was wondering if there was a way to deploy images to clients only for PXE. I don't want to advertise the image/Task sequence to collection for them to cache. I want to just be able to PXE boot a machine at any given point. Any ideas? Thanks
  7. Well i tried everything with no luck...i uninstalled the WinAIK and installed the new Windows 7 AIK a new Boot PE no go....just the same old Vista boot. I even built a test WDS server in my test lab loaded up the custom PE and that comes down without any issues with the Windows 7 Boot screen. not sure what the problem is with SCCM not using the right boot screen. If anyone has the solution let me know.
  8. Yeah everything is working fine....i just would like to nice boot screen for windows 7 then Vista. Let me know if you find a solution for this. I am going to work on some things today, if i find a fix i will post it up on here.
  9. I created a Windows 7 PE on another server with WAIK for Windows 7 installed and also injected the required WMI packages. I was able to import the wim into SCCM as a boot image and added to DP. When I PXE boot a machine it still shows the vista boot screen rather then the new Windows 7 boot screen. I have WAIK 2.0 which was installed by default with SCCM SP2, is it not compatible with WINPE 3.0? I deleted all other Boot images from DP and only left the Windows 7 PE which i imported, still when the machine boots it retains the old vista boot screen?? When i create an ISO of the boot wim and manually boot a machine from it, it uses the new Windows 7 Boot screen...Not sure what the problem is with the SCCM PXE not displaying the new boot screen. do i need to uninstall WAIK 2.0 and install the new WAIK for Windows 7?
  10. Hello, I was looking for someone that has good VB scripting backgound that could give me a hand. Our enterprise is pretty much an all Dell shop, and our techs name the machines with the Dell service tag mainly for asset tracking. Now, I setup a Task Sequence for OSD and advertised it to the "All Unknown Computers" collection for all bare metal machines. Now I have a working script that I added into the TS that will bring up a pop-up box asking for the machine name (i know you can set this as a variable in the collection, but i like the script better), here is the script i am using for that: Dim sNewComputerName, oTaskSequence, sTSMachineName Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") ' Get the name the computer is set to receive and truncate to first 6 letters sTSMachineName = oTAskSequence("_SMSTSMachineName") sTSMachineName = lcase(left(sTSMachineName,6)) If sTSMachineName = "minint" Then ' The wscript.echo commands are logged in SMSTS.log for troubleshooting. ' They are not displayed to the end user. wscript.echo "Detected that the computer name is scheduled to receive a random value. Prompting user to input a standard name." sNewComputerName = InputBox ("Please enter a standard computer name.", "Computer Name", , 30,30) oTaskSequence("OSDComputerName") = sNewComputerName wscript.echo "Set Task Sequence variable OSDComputerName to: " & sNewComputerName Else wscript.echo "Computer set to receive a standard name, continuing as is." End If NOW, rather than having the script ask for a computer name and have the tech enter the asset/service Tag off the Dell, i would like to have a script like the one above, but rather than asking to enter the computer name, i would like to query the BIOS for the Dell asset tag and automatically use the results as the OSDComputerName. I have the VBS that gets the information i need from the BIOS but i can't for some reason get it to work with the TS, keeps erroring out of me. I tried to take peices from the ove script and added some lines from the below script with no luck. If anyone has a script or knows how to create one with what i have let me know. Thanks for the help/ DELL BIOS VBS Set objWMIservice = GetObject("winmgmts:\\.\root\cimv2") set colitems = objWMIservice.ExecQuery("Select * from Win32_BIOS",,48) For each objitem in colitems Wscript.echo objitem.serialnumber Next
  11. That is the best solution...I never even thought about something like that! I just set it up for "Windows 2000" Machines (which we don't have any of) worked like a charm. How can u PXE a machine that has already been imaged with the TS. For example, i image a new machine with Windows 7, but later down the road that same machine needs to be reimaged again. When I try to re-image a machine that already had a TS advertised to before always aborts the PXE. I would like to be able to image a machine at any given point, even if it has already been imaged with the same TS already. I tried hitting the Clean Last PXE Advertisment for the collect that the TS is advertised to, but get mixed results for some reason. Would like to always have the option to hit F12 at any given point in PXE rather than getting aborted. Let me know.
  12. OK i got it to work....simply by adding the deployment task for Software Updates to the All Unknown Computers collections. Worked like a charm. Now this is something that has been bugging me for awhile now..How do i keep a running advertisment for OSD task sequence to lets say "All Windows 7 systems" collection that i created, but for only PXE. I want to be able to keep a running advertisment for this collection just for clients to be able to hit F12 and boot from NIC, but don't want the clients to recieve the advertisment and cache to local disk. is there a way. I created a TS for OSD and advertised it as a non-mandatory. I can PXE any machine in the collectio without any issues, but i noticed that all the clients have recieved the advertisment but just didn't run. Any help would be great...will it work if i only set the DP's for the bootPE and system image to only the SMSPXE DP? Thanks.
  13. Well that is the tricky part, these are all unknown computers, i have the task sequence advertised for the "All Unknown Computers" collections but when a Unknown Computer gets the Advertisment for the task sequence it is then placed into Unprovisioned Computers under Operating System Deployment. It never becomes part of any collection until the client is installed an performs a software inventory. Getting back to your reply I advertised the Software Deployment task to all systems, i figured the unknown computer would show up in that collection even though it hasn't fully had a software inventory performed...Let me know what you think, or if there is another way to perform software updates on Unknown Computers. Thanks
  14. Hello, I am looking for some help....I am in the process of deploying Windows 7 to our environment, PXE is working great with deploying a custom Windows 7 WIM image. My question is how do i install Software updates within the task sequence? I have selected to install All Mandatory Updates which didn't work, I also selected the option to install All Updates with no success. I have setup the deployment of the patches that i want to be installed and advertised them to both distrubution points including the SMSPXE DP. For some reason when it hits the task sequence to install updates it seems to skip over the step like there is nothing to install and continues on installed software packages that i assigned to the Task Sequence. Any help with deploying Software Updates in PXE Task Sequence would be great...
  15. I would uninstall the WDS from your DC and then install on your SCCM Server. Don't configure WDS..then install SCCM PXE Site role. Also, if you are trying to deploy images to clients on a different vlan then what your WDS server is located you will need to add option 66 and 67 to your DHCP server and make sure you have IP helps on the switches.. Add the following DHCP Scope Options: 066 IP Address of WDS Server 067 boot\x86\wdsnbp.com
  16. I have another issue....the MP installs fine, i have green checks for everything, problem now is that I cannot deploy the clients to machines. When i look in the system32/ccmsetup folder the log files says that it cannot find the ccmsetup.cab file in location http://SCCM.domain1.local/CCM_Client web location. I also can't connect to the SMSreporting_ site... Anyone know why...i am thinking IIS permissions or authorization problems, because when i browse from localhost on SCCM server everything is fine.
  17. I had the same issue. My fix was just to install WebDAV but didn't configure until SCCM SP2 was installed. It will say at the end of the install that the MP installation was unknown and you will also get the error you provided. Once you see that follow these direcions: Enable WebDAV and create an Authoring Rule, as follows: 1. Navigate to Start / All Programs / Administrative Tools / Internet Information Services (IIS) Manager to start Internet Information Services 7 Application Server Manager. 2. In the Connections pane, expand the Sites node in the navigation tree, and then click Default Web Site if you are using the default Web site for the site system or SMSWEB if you are using a custom Web site for the site system. 3. In the Features View, double-click WebDAV Authoring Rules. 4. When the WebDAV Authoring Rules page is displayed, in the Actions pane, click Enable WebDAV. 5. After WebDAV has been enabled, in the Actions pane, click Add Authoring Rule. 6. In the Add Authoring Rule dialog box, under Allow access to, click All content. 7. Under Allow access to this content to, click All users. 8. Under Permissions, click Read, and then click OK. 4. Change the property behavior as follows: 1. In the WebDAV Authoring Rules page, in the Actions pane, click WebDAV Settings. 2. In the WebDAV Settings page, under Property Behavior, set Allow anonymous property queries to True. 3. Set Allow Custom Properties to False. 4. Set Allow property queries with infinite depth to True. 5. If this is a BITS-enabled distribution point, under WebDAV Behavior, set Allow hidden files to be listed to True. 6. In the Action pane, click Apply. 5. Close Internet Information Services (IIS) Manager. To add Remote Differential Compression for site server and branch distribution point computers 1. In Server Manager, on the Features node, click Add Features to start the Add Features Wizard. 2. On the Select Features page, select Remote Differential Compression, and then click Next. 3. Complete the rest of the wizard. 4. Close Server Manager. To modify the requestFiltering section on BITS-enabled distribution point computers: 1. Open the applicationHost.config file located in the %windir%\System32\inetsrv\config\ directory on the BITS-enabled distribution point site system. 2. Search for the <requestFiltering> section. 3. Determine the file extensions that you will have in the packages on that distribution point. For each file extension that you require, change allowed to true. For example, if your package will contain a file with an .mdb extension, change the line <add fileExtension=".mdb" allowed="false" /> to <add fileExtension=".mdb" allowed="true" />. Allow only the file extensions required for your packages. 4. Save and close the applicationHost.config file.
  18. I have been rolling out Server 2008 Enterprise x64 on about a dozen servers now. All seem to communicate back to SCCM server with data, problem is when I look in control panel i do not see the normal icons as i do in server 2003 and xp workstations. I looked in the windows SystemWOW64 folder and do have client folder which has all the required apps. Also nothing showing up in program and features to having a client installed. Anyone having this issue or know where to look?
  19. Hello, I am in the process of creating custom Boot PE images for SCCM. I have successfully created my own x86 and x64 Boot PE images and was able to add them to SCCM, my problem is with ia64. I am using WindowsAIK 1.1 on a stand alone machine and using the same steps as the previous custom boot PE's that I created that worked perfectly in SCCM. Here are the steps I am taken: Copype ia64 %rootdirectory% Once copied i then mount the image, once mounted I added the 3 required components for SCCM (*Scripting* *WMI* *XML*) they all install fine. Then I inject the drivers that i need for my environment which they all added fine. Once that is completed i then finalize which completes and then unmount the wim. I then copy this folder to the SCCM directory which holds all the other custom Boot PE's that i created which has all the correct permissions needed because I have used all the others fine. When i go into the admin counsel to add a new boot image, i am able to select the wim from UNC path scrolls through working a few times then I get an error, stating that i need to make sure that the folder or files are not "read only" and have permissions to modify the file. Permissions are set the same as all the others and I don't have any issues with those. Any help would be great. Thanks
  20. Hello All, I am doing a simple image deployment of the install.wim in the source folder that comes with the Server 2008 CD. I have added the install.wim to operating system images and created a task sequence using just the wim. I didn't create a package for the root of the ISO as shown in the set by step document on this site. Anyway, the install.wim deploys fine, everything boots all drivers load that I have loaded in SCCM, the only problem I am having is that the system drive keeps reverting to the D: drive.....Anyway around this????
  21. I found the easiest way for XP is to install it on a base machine, install all drivers and apps, sysprep shutdown. Boot with WinPE cd with imagex injected into and capture your wim. Copy to SCCM shared folder and deploy.
  22. Does the client pickup the TFTP Boot? Once it picks up the Boot you should see the IP in the lower left hand corner before it finishes loading the PE. Also if your on a static subnet, you may need to create a DHCP Pool for a certain amount of IPs you may need.
  23. That's a nice trick with Firefox, I am gonna give it a try. You have any info on SCOM?
  24. Hello All, I was just looking for some advice. I just installed System Center Updates Publisher 4.5 on the same server as my SCCM. Everything works fine, created self signed Certs to be able to publish the data etc.. Found the URL for Adobe's catalog files, created a new vendor for Adobe and flagged bother versions of Flash player, published them and was able to sync them to my SCCM SUP. Everything shows up great, what clients are in need or have already downloaded the patch. Same setup as if you were deploying Windows Updates. Here is my question, does anyone know of a way to get a catalog file for Firefox?? Deploying a silent package of this is a pain, gotta extract the setup file for each new version (Which is like twice a month...) and create a custom 7-Zip package to deploy to clients silently. Also maybe any other vendors like Java, or possibly catalogs for Acrobat. If anyone knows of any sites with info would be great. I looked at M$ sites regarding this and they say they only support Dell, HP, Intel and Citrix which is a lie because I have adobe working just fine. I do remember Adobe being one of those partners but just isn't listed anymore. Thanks..
×
×
  • Create New...