Jump to content


simulacra75

Established Members
 View Profile  See their activity

  • Posts

    141

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by simulacra75

  1. simulacra75
    AFAIK, you cannot use a 64-bit boot image in your TS because the Lenovo BIOS Flash utility only supports the x86 architecture. On top of this you need to add a specific "Run Command Line" that does a "full" restart of the target computer, cmd.exe /c shutdown /s /t 0 /f That should do it but if you cannot use an x86 boot image, you're screwed until Lenovo provide an 64-bit compatible Flash utility
  2. simulacra75
    I do not know if it will work on Thinkcentre products. Best thing you can do, is run the powershell commands on some of the models and see if you get output. That will tell you if it works or not.
  3. simulacra75
    Well then, that's different! Okay. Lenovo make things a little easier because they expose the BIOS settings to WMI. This means you can use Powershell, for example, to get settings from WMI and also to change them. Display all BIOS Settings in Powershell gwmi -class Lenovo_BiosSetting -namespace root\wmi | ForEach-Object {if ($_.CurrentSetting -ne "") {Write-Host $_.CurrentSetting.replace(","," = ")}} Get all possible values for a particular setting (TPM chip in this example) (gwmi –class Lenovo_GetBiosSelections –namespace root\wmi).GetBiosSelections("SecurityChip") |Format-List Selections Change and save a BIOS setting (making TPM active in this example. Note the 2 step process, changing the value and then saving said value. Also note the setting string is case-sensitive) (gwmi -class Lenovo_SetBiosSetting –namespace root\wmi).SetBiosSetting("SecurityChip,Active") (gwmi -class Lenovo_SaveBiosSettings -namespace root\wmi).SaveBiosSettings() That should be enough to get you started i think. Probably worth pointing out that changing BIOS settings via Powershell is not supported on ALL Lenovo models. Give it a try though.
  4. simulacra75
    Not entirely sure why you're trying to get BitLocker to work with Windows 7 Professional, because it doesn't/cannot work. It's not implemented in Windows 7 Professional. You need to have Windows 7 Ultimate or Enterprise to use BitLocker.
  5. simulacra75
    Just a tip or something to be aware of. One of my admins pointed out they were running low on disk space on the drive where the SQL server was installed. Turns out that by default the ReportServer DB log file is set to grow to 2TB by default! Went into SSMS and changed the ReportServer DB to "simple" and then ran the "shrink" command on the log file of that DB. File went from 500+GB to 6MB. Changed to the maximum file size afterwards too so it doesn't happen again. Thought some of you might find this useful.
  6. simulacra75
    IP address change shouldn't be a problem, so long as it updates in DNS
  7. simulacra75
    Okay. Lets see if WMI is a problem. Open an admin command prompt and run the below commands, in order. 1). net stop winmgmt /y (this will stop WMI and all it's dependent services) 2). winmgmt /resetrepository (resets WMI completely. Check the Application log in Event viewer to see when it's complete. Should take no more than 2 minutes in total) 3). Try installing the client again and see what happens
  8. simulacra75
    Is the account been used to perform the installation an administrator of the client machine where the install is attempting to take place?
  9. simulacra75
    Hope this isn't a stupid question but i was wondering if both the Windows Setup Compatibility Scan and the actual upgrade (assuming the compatibility scan was successful) could be incorporated into the same TS? Is this even possible? Anyone tried to get it to work?
  10. simulacra75
    Hi Niall Just something to point out to you. The script "wrapper.vbs" refers to a "TargetBuild" number. This would need to be changed manually if upgrading to 1703 (need to be changed to 15063, if i'm not mistaken) and this isn't referred to in the guide. Thought you'd like to know. Thanks
  11. simulacra75
    I believe i have finally figured this one out. This issue occurs if there is a Software Updates that has completed, but still has a pending restart. At least that's what i am seeing in my environment.
  12. simulacra75
    Maybe you could take a look at this? I tried it out a couple of years ago as a test and it did work then. Can't say for sure if it would still work today however.
  13. simulacra75
    Whilst testing the 1703 servicing update for Windows 10 i've noticed that in the pre-install stages there is a "scan" carried out by the update process on the client machine to try and detect incompatible applications and a hard stop occurs if an incompatible application is found. This is good, in the sense that it will try and leave a machine in full working order, post-install. The gripe that i have with it though is that the update process needs to be triggered in the first place to find out what incompatible apps are going to prevent the install from finishing successfully. What i was hoping for was an app/package that i could use to "scan" all my applicable clients before attempting the rollout of the servicing update to see what incompatible apps exist (if any) and re-mediate these issues before beginning a production rollout of the servicing update. Anyone come across something like this?
  14. simulacra75
    Here is a guide from MS. Have you done this part? If Yes, check the registry on the client machine at HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate. In here you should see entries for WUServer and WUStatusServer. The values for these entries should be the Primary Site server, if you have everything setup correctly, e.g. http://<Primary Site Name>:8530
  15. simulacra75
    That's not a trivial task. You cannot do an inplace upgrade to the current infrastructure so i'd suggest that you stand up a new Primary Site with v1702 and point it to a newly created DB on the cluster. You'd then need to create "migration" jobs that would attempt to pull over everything from the "old" site to the "new". This is documented on several wesbites, here is an example. Respectfully, you don't sound you've done "full" CM administration before so be careful and try and read up on as many topics as possible in relation to administration and setup of new Primary Sites in CM12.
  16. simulacra75
    Not much point attempting to glean data from the CM12 DB using a WMI query that's designed to query a machine, you wouldn't be comparing apples with apples. If you really want to test it properly then you would need to execute the WMI query on the "targeted" machines and verify that the result is what you expect. You do not have to use WBEMTEST for this, it's possible in a lot of WMI queries to query the machine remotely using the pstools command line; e.g. psexec \\<Machine-Name or IP Address> wmic computersystem get model (This would return the model of the machine as contained within the computersystem class) Here's a link to some useful WMIC queries
  17. simulacra75
    The error, 0x8004100e, translates to "Invalid WMI namespace". I would run a repair of WMI on the machines that are giving that error.
  18. simulacra75
    There's a specific Rule in Dynamic Variables called "Location". Perhaps you should read up on it.
  19. simulacra75
    Dynamic Variables in your Task Sequence sound like they will do what you're looking for. It's under the "General" section of the Add Menu of a Task Sequence
  20. simulacra75
    Windows Firewall and Port Settings for Client Computers in Configuration Manager
  21. simulacra75
    Is the firewall enabled on all your client machines? If it is, you could dry disabling the firewall temporarily on a few clients, restart them and then try the installation again on those clients. I should have pointed out in my first post, are you able to browse to those remote clients, using the Network Service Account from the Primary Site that's attempting the installation process. It's important that the client is accessible from the Primary Site itself, obviously.
  22. simulacra75
    Are there services not running on the remote clients that the Client Push requires in order to connect to the admin$ share? For example, RemoteRegistry? Have you tried manually connecting to these remote machines \\machine-name\admin$ with the network account? If you're getting an error, what is that error when you try manually?
  23. simulacra75
    Short answer, No. Not possible. To my knowledge, the boot image that is chosen by PXE is the boot image associated with the most recently edited Task Sequence. You can "force" boot image selection if you create bootable USB media with the desired boot image but that's the only way that i know of doing it. I understand that with 1702 there's an option to assign an expiry date on boot images so you could, in theory, force folks to update their boot media on a regular basis but that's another topic entirely.
  24. simulacra75
    What versions are going from and to? Any log files?
  25. simulacra75
    Yes, you would need a Boundary Group at that location, with a reference to the DP that you're going to setup. You could also use AD as your Boundaries, if you have all those VPN-located clients in the same AD OU,
×
×
  • 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.