28.6.13

Как убрать надпись "Powered by Phoca Guestbook 2.07"

Powered By линк скрыт в этом файле : components/com_phocaguestbook/helpers/phocaguestbook.php
176 строчка
 
function getInfo() {
    return base64_decode('PGRpdiBzdHlsZT0idGV4dC1hbGlnbjogcmlnaHQ7IGNvbG9
                          yOiNkM2QzZDM7Ij5Qb3dlcmVkIGJ5IDxhIGhyZWY9Imh0d
                          HA6Ly93d3cucGhvY2EuY3oiIHN0eWxlPSJ0ZXh0LWRlY29
                          yYXRpb246IG5vbmU7IiB0YXJnZXQ9Il9ibGFuayIgdGl0bGU
                          9IlBob2NhLmN6Ij5QaG9jYTwvYT4gPGEgaHJlZj0iaHR0cDo
                          vL3d3dy5waG9jYS5jei9waG9jYWd1ZXN0Ym9vayIgc3R5b
                          GU9InRleHQtZGVjb3JhdGlvbjogbm9 uZTsiIHRhcmdldD0iX
                          2JsYW5rIiB0aXRsZT0iUGhvY2EgR3Vlc3Rib29rIj5HdWVzd
                          GJvb2s8L2E+PC9kaXY+');
}


Оставляем вот так:
function getInfo() {
        return;
     }

http://www.mysysadmintips.com/other/web/295-edit-or-remove-powered-by-phoca-guestbook-back-link



25.6.13

SCCM 2012 запросы(query )

links
Computers with certain prefixes - % being a wildcard

   select SMS_R_System.NetbiosName
  from
   SMS_R_System
   WHERE
   SMS_R_System.NetbiosName = "ABC%"  

Adobe Reader XI Installations - from Programs in Control Panel


 select SMS_R_System.NetbiosName,  
 SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName from  
 SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on  
 SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId =  
 SMS_R_System.ResourceId where  
 SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like “Adobe Reader XI”  

Devices based on OU


  select distinct * from SMS_R_System
 WHERE
 SMS_R_System.SystemOUName = "OU NAME"  

Windows 8 Installations


 select SMS_R_SYSTEM.ResourceID,  
 SMS_R_SYSTEM.ResourceType,
 SMS_R_SYSTEM.Name,
 SMS_R_SYSTEM.SMSUniqueIdentifier,  
 SMS_R_SYSTEM.ResourceDomainORWorkgroup,
 SMS_R_SYSTEM.Client from SMS_R_System   
 INNER JOIN 
 SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId   
 WHERE
 SMS_R_System.OperatingSystemNameandVersion 
 LIKE
 "%Workstation 6.2%" or SMS_R_System.OperatingSystemNameandVersion LIKE "%Windows 8%"  

EventList 1.0.2 русский язык

24.6.13

silent uninstall yandex bar

@echo off
REM Яндекс.Бар 6.0 для Internet Explorer
MsiExec.exe /qn /norestart /x{35015585-072D-4D95-9509-E6205C6F7991} /l*v C:\Temp\yandexbar.log
Rem Яндекс.Бар 4.2 для Internet Explorer
MsiExec.exe /qn /norestart /X{6740F9E3-1353-47DD-9765-BA49FC4C3479} /l*v C:\Temp\yandexbar.log
Rem Яндекс.Бар 4.3 для Internet Explorer
MsiExec.exe /qn /norestart /X{C114D9A9-C884-45EA-A3FA-020B867AADCF} /l*v C:\Temp\yandexbar.log
rem Яндекс.Бар 5.2 для Internet Explorer
MsiExec.exe /qn /norestart /X{D69BC815-E103-4689-9D27-71894EF6EE6A} /l*v C:\Temp\yandexbar.log
REM Яндекс.Бар 5.2 для Internet Explorer Version : 5.2.2.1310
MsiExec.exe /qn /norestart /X{F75CF7C3-AB31-4E4E-A38D-051D634EE2A6} /l*v C:\Temp\yandexbar.log
REM Яндекс.Бар 5.3 для Internet Explorer   
MsiExec.exe /qn /norestart /x{FBB54511-4D35-4EE0-872C-BB5A9617EC8F} /l*v C:\Temp\yandexbar.log
rem Яндекс.Бар 6.5 для Internet Explorer
MsiExec.exe /qn /norestart /X{FBFBBDD0-EC37-4152-BB77-7D54322AF953} /l*v C:\Temp\yandexbar.log
REM Яндекс.Бар 6.7 для Internet Explorer
MsiExec.exe /qn /norestart /X{11EA1C75-DB0D-410B-B63B-20916EECD568} /l*v C:\Temp\yandexbar.log
Rem uninstall yandex bar  in win7x64 and ie10 addons
reg delete "HKCR\Wow6432Node\CLSID\{91397D20-1446-11D4-8AF4-0040CA1127B6}" /f
reg delete "HKCR\Yandex.Toolbar" /f
reg delete "HKCR\Yandex.Toolbar.1" /f
reg delete "HKCR\Software\Microsoft\Internet Explorer\Toolbar\webbrowser" /v {91397D20-1446-11D4-8AF4-0040CA1127B6} /f
reg delete "HKLM\SOFTWARE\Microsoft\Internet Explorer\Extension Compatibility\{91397D20-1446-11D4-8AF4-0040CA1127B6}" /f
reg delete "HKLM\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Toolbar" /f
reg delete "HKEY_USERS\.DEFAULT\Software\Microsoft\Internet Explorer\Toolbar\WebBrowser" /v {91397D20-1446-11D4-8AF4-0040CA1127B6} /f

20.6.13

Удаление клиента SCCM2012

C:\windows\ccmsetup\Ccmsetup.exe /uninstall и нажмите клавишу ВВОД.

Устранение неполадок развертывания Sccm

Коды настраиваемых ошибок развертывания операционной системы

 

Код ошибки Возможная проблема Возможное решение
0x80040001 Не удалось получить GUID клиента Проверьте, импортирован ли компьютер в базу данных сайта. Дополнительные сведения см. в файле clientidmgr.log в папке точки управления (MP).
0x80040101 Не задана учетная запись доступа к сети Проверьте пользовательский интерфейс администратора и убедитесь, что учетная запись доступа к сети установлена
0x80040102 Не возвращено расположение содержимого для заданного пакета Проверьте сервер и убедитесь, что пакеты распространяются не менее, чем на одну точку распространения. Также проверьте, позволяет ли объявление последовательности задач использовать удаленную точку распространения при отсутствии локальной
0x80040103 Не удалось получить доступ к содержимому пакета в точке распространения Убедитесь, что учетная запись доступа к сети установлена правильно. Проверьте подчеркнутое сетевое подключение.
0x80040104 Не удалось найти политику программы ссылок Убедитесь, что политика программы ссылок загружается локально. Дополнительные сведения см. в журнале агента политик.
0x80040105 Не удалось найти необработанную политику CCM_ClientAgentConfig Убедитесь, что политика загружается локально. Дополнительные сведения см. в журнале агента политик.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Указан недопустимый путь к сохраненному образу. Введите допустимый путь.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Указано недопустимое расширение имени файла образа. Введите допустимое расширение имени файла (.WIM)
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) Указано недопустимое имя файла образа. Введите допустимое имя файла.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Слишком длинный путь к сохраненному образу Введите допустимый путь
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) Указано недопустимое имя файла образа. Введите допустимое имя файла
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Для PNP истекло время ожидания завершения инициализации. Проверьте журналы Windows
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Не удалось выполнить последовательность задач в Windows PE Дополнительные сведения см. в файле smsts.log.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Указан недопустимый индекс сетевого адаптера Данный сетевой адаптер не найден. Проверьте, установлены ли правильные драйвера.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Не установлен Sysprep Установите правильную версию sysprep
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Недопустимый Sysprep Установите правильную версию sysprep
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) Недопустимый системный раздел Проверьте список поддерживаемых типов системных файлов в документации к OSD.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Компьютер присоединен к домену Отсоедините компьютер от домена и выполните перезапуск
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) Компьютер является контроллером домена Контроллеры доменов не могут быть использованы в качестве исходных компьютеров
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Для этого сайта не назначена точка управления по умолчанию. Задайте точку управления по умолчанию
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Недоступны сертификаты для точки управления по умолчанию. Повторите попытку
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) Пакет {0} недоступен на указанных точках распространения. Назначьте пакет точке распространения
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Недопустимый пароль для сертификата носителя Укажите допустимый пароль
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) У сертификата носителя нет связанного закрытого ключа Создайте сертификат носителя с закрытым ключом
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,6) Для этого сайта не задан сертификат центра сертификации. Задайте центр

Collection Queries (Колекции запросов ) SCCM2012

Author link:
http://myitforum.com/cs2/blogs/rbennett806/pages/collection-queries.aspx

Collection Query IconOU-Based
If you wish to target specific sections of your Active Directory infrastructure, then you may wish to utilize collections based on computer account object OUs; making sure to watch out for oddities if using subOU levels.
select * from SMS_R_System where SMS_R_System.SystemOUName = "MyDomain.com/OU/SubOU"
Limit to collection: (your collection of healthy clients)
Notes: Remember, currently SCCM is Active Directory (AD) aware, not AD-integrated. This means there is still a lag in time between what's happening in AD and what the SCCM service knows. If you require a more immediate result, you may want to look into using scripts instead of the normal consoles.

Collection Query IconHealthy Clients (3 queries)
Now, I'm a big believer that every collection query should be limited. What this does is ensures that your query is running against the desired pool of clients; which hopefully means that you won't get unexpected results. If you're new to SCCM (and maybe even if you aren't), I'd strongly recommend first coming up with a strategy on weeding out your inactive/unhealthy clients from your healthy ones. Then, once you have a collection of known, healthy and active clients, you can use that collection to limit all of your others. This way you don't spend time trying to deploy an item to a client that's not communicating correctly in the first place.
LAPTOPS: select * from SMS_R_System where ResourceID in (select SMS_R_System.ResourceID from SMS_R_System where (SMS_R_System.SystemOUName = "MyDomain.com/OU/SubOU" or SMS_R_System.SystemOUName = "MyDomain.com/OU2")) and ResourceID in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceID where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in ( "8", "9", "10", "11", "12", "14", "18", "21" )) and ResourceID in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceID where DATEDIFF(dd,SMS_G_System_WORKSTATION_STATUS.LastHardwareScan,GetDate()) < 90)
VIRTUAL PCS: select * from SMS_R_System where ResourceID in (select SMS_R_System.ResourceID from SMS_R_System where (SMS_R_System.SystemOUName = "MyDomain.com/OU/SubOU" or SMS_R_System.SystemOUName = "MyDomain.com/OU2")) and ResourceID in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceID where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in ( "1", "2", "3", "4", "5", "6", "7", "13", "15", "16", "17", "19", "20", "22", "23", "24" )) and ResourceID in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceID where (SMS_G_System_COMPUTER_SYSTEM.Model in ("Virtual Machine", "VMWare Virtual Platform", "Parallels Virtual Platform"))) and ResourceID in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceID where DATEDIFF(dd,SMS_G_System_WORKSTATION_STATUS.LastHardwareScan,GetDate()) < 90)
OTHER: select * from SMS_R_System where ResourceID in (select SMS_R_System.ResourceID from SMS_R_System where (SMS_R_System.SystemOUName = "MyDomain.com/OU/SubOU" or SMS_R_System.SystemOUName = "MyDomain.com/OU2")) and ResourceID in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceID where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in ( "1", "2", "3", "4", "5", "6", "7", "13", "15", "16", "17", "19", "20", "22", "23", "24" )) and ResourceID not in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceID where (SMS_G_System_COMPUTER_SYSTEM.Model in ("Virtual Machine", "VMWare Virtual Platform", "Parallels Virtual Platform"))) and ResourceID in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceID where DATEDIFF(dd,SMS_G_System_WORKSTATION_STATUS.LastHardwareScan,GetDate()) < 45)
Limit to collection: (not limited)
Notes: In our environment, while we could have used a complex process, we decided that since we're in one basic geographical location, that we'd deem a client as being "healthy" if it reported its Hardware Inventory information every 90 days for a laptop or virtual machine, and 45 days for anything else (like desktops).

Collection Query IconUnhealthy Clients
These are basically the clients that aren't in the healthy collection, and probably need a little manual intervention (even if it's just reminding the end user to connect their laptop to the internet or the VPN).
select * from SMS_R_System where ResourceID in (select SMS_R_System.ResourceID from SMS_R_System where (SMS_R_System.SystemOUName = "MyDomain.com/OU/SubOU" or SMS_R_System.SystemOUName = "MyDomain.com/OU2")) and ResourceID not in (select ResourceID from SMS_FullCollectionMembership where CollectionID = "XXXXXXXX")
Limit to collection: (maybe use an OU-based collection)
Notes: Every environment is different, so keep in mind that these are just suggestions and examples.

Collection Query IconAdobe Reader
You will need to use the correct name and version number to get the needed collection. You may easily find this information in the registry and/or by using Resource Explorer within the ConfigMgr console.
select * from SMS_R_System where SMS_R_System.ResourceID not in (select SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID from SMS_G_System_ADD_REMOVE_PROGRAMS where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Adobe Reader 10.0.1" and SMS_G_System_ADD_REMOVE_PROGRAMS.Version = "10.0.1")
Limit to collection: (your collection of healthy clients)
Notes: I would strongly recommend staying away from the ">", "<", "+" operators when dealing with version numbers. While there's a lengthy answer as to why, the quick answer is that things like 9.0.123 is not a real number (multiple decimal points).

Collection Query IconMozilla Firefox
This is another sample that is identical to the Adobe Reader query so that you may see how you can quickly change a few pieces of information to obtain the desired result.
select * from SMS_R_System where SMS_R_System.ResourceID not in (select SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID from SMS_G_System_ADD_REMOVE_PROGRAMS where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Mozilla Firefox (3.6.13)" and SMS_G_System_ADD_REMOVE_PROGRAMS.Version = "3.6.13 (en-US)")
Limit to collection: (your collection of healthy clients)
Notes: Try to stay away from mathematical operations using the version number.

Collection Query IconSun JAVA
Yet another query identical to the Adobe Reader and the Mozilla Firefox queries.
select * from SMS_R_System where SMS_R_System.ResourceID not in (select SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID from SMS_G_System_ADD_REMOVE_PROGRAMS where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Java(TM) 6 Update 20" and SMS_G_System_ADD_REMOVE_PROGRAMS.Version = "6.0.200")
Limit to collection: (your collection of healthy clients)
Notes: If you need a more flexible query, try using the wildcard character (%). So instead of using "6.0.200" you could try using something like "6.0.%".

Collection Query IconInternet Explorer 9Identify Windows 7 clients that already have IE 9.x installed.
select * from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceID inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceID where SMS_G_System_SoftwareFile.FilePath like "%\\Program Files\\Internet Explorer\\" and SMS_G_System_SoftwareFile.FileName like "iexplore.exe" and SMS_G_System_SoftwareFile.FileVersion like "9.%" and SMS_G_System_OPERATING_SYSTEM.Version like "6.1%"
Limit to collection: (your collection of healthy clients)
Notes: To find the clients that have not yet installed IE 9, simply change "like" to "not like" when checking the file verison number. Also, if you see oddities in the memberships, keep in mind that this is based off of the .EXEs polled and listed in the SCCM database, so when in doubt, use Resource Explorer within the ConfigMgr console to see if the "iexplore.exe" file has been inventoried.

Collection Query IconOffice 2007 Enterprise
This query will generate a collection of clients that have Office 2007 Enterprise edition installed.
select * from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceID where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft Office Enterprise 2007"
Limit to collection: (your collection of healthy clients)
Notes: While similar to the Adobe Reader, Mozilla Firefox, and Sun JAVA collections, note that this one does not rely on the DisplayVersion information as we want to know where it's installed, regardless of the exact version.

Collection Query IconSCCM Client Version
When deploying a newer version of the SCCM client, a collection may come in handy to locate those machines not up to speed.
select * from SMS_R_System where SMS_R_System.ResourceID not in (select ResourceID from SMS_R_System where SMS_R_System.ClientVersion = "4.00.6487.2000")
Limit to collection: (your collection of healthy clients)
Notes:

Collection Query IconNot A Member of CollectionX
Often you have an existing collection that is being used for something else, and you simply want to generate a collection of machines that are NOT in that collection.
select * from SMS_R_System where ResourceID not in (select ResourceID from SMS_FullCollectionMembership where CollectionID = "XXXXXXXX")
Limit to collection: (your collection of healthy clients)
Notes: It is recommended that you build a query that's based on some other criteria, but this one can be used in a snap when you need to quickly deploy something to a set of clients.

Collection Query IconLaptop Machines
This query will generate a collection that should contain only laptop devices.
select * from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceID where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in ( "8", "9", "10", "14" )
Limit to collection: (your collection of healthy clients)
Notes: You may wish to ensure that the model types used in the sample query are correct for your environment.

Collection Query IconDell Client Machines
This query will generate a collection that should contain only Dell clients.
select * from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceID where SMS_G_System_COMPUTER_SYSTEM.Manufacturer like "Dell%"
Limit to collection: (your collection of healthy clients)
Notes: Depending on when the PC was purchased, and what BIOS level it's at, the manufacturer name could be one of several variations. Thus we use the wildcard character in this example in order to get around the problem.

Collection Query Iconx64 Operating Systems
This query will generate a collection of clients that are running a 64-bit operating system.
select * from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceID where SMS_G_System_COMPUTER_SYSTEM.SystemType = "x64-based PC"
Limit to collection: (your collection of healthy clients)
Notes: If you wanted a collection of 32-bit operating systems you could query for "x86-based PC" instead.

Collection Query IconWindows 7 Operating Systems (without any Service Packs)
This query will generate a collection of clients that are running Windows 7, but have yet to install any service packs.
select * from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceID where SMS_G_System_OPERATING_SYSTEM.Version = "6.1.7600"
Limit to collection: (your collection of healthy clients)
Notes: If you wanted a collection of Windows 7 SP1 clients, use 6.1.7601 for the version number, or for ALL versions of Windows 7, you could toss in a wildcard and use "6.1%" (may need to also change "=" to "like"). Please note that this doesn't take into account servers. So if you have them within SCCM, double-check the version number you really want to use.

Collection Query IconWindows XP Operating Systems
This query will generate a collection of clients that are running a version of the Windows XP operating system.
select * from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceID where SMS_G_System_OPERATING_SYSTEM.Caption like "% Windows XP %"
Limit to collection: (your collection of healthy clients)
Notes: This query uses the wildcard character so as to not be specific on the exact version.

Collection Query IconFile-Based
This query will generate a collection of clients that do not have the listed .EXE file within the given path.
select * from SMS_R_System where SMS_R_System.ResourceID not in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceID where SMS_G_System_SoftwareFile.FileName = "MyFile.exe" and SMS_G_System_SoftwareFile.FilePath like "%\\Program Files\\Folder\\Subfolder\\%")
Limit to collection: (your collection of healthy clients)
Notes: If you wanted to get even more specific you could also check for the DisplayVersion.


NOTE 1: Dynamic collection queries are ones where a client should drop out of the collection automatically if it no longer meets the requirements. For example, if the client doesn't have ApplicationX installed, when the query runs it will add the client to the collection. Assuming there is an advertisement targeted to the collection that installs ApplicationX, once the client reports back to the SCCM server that ApplicationX has installed (normally via the Hardware Inventory), then the next time the collection query runs, the client will be automatically removed from the collection. The nice part about a dynamic collection is that if ApplicationX were to be removed, then once that is reflected in the SCCM database, the next time the query runs, the client will be added back into the collection again. Then, assuming that your advertisement is set to reoccur and to run again, the client will have ApplicationX installed again.
NOTE 2: The Add/Remove Programs information is pulled into the SCCM database via the Hardware Inventory scan, and not the Software Inventory scan as one might think.
NOTE 3: If you wish to verify information about an installed piece of software, you may use the Registry Editor on a machine and look in the following subkey locations:
32-bit Application: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
64-bit Application: HKLM\SOFTWARE\ Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

NOTE 4: I have intentionally tried to not use aliases for the names within the queries in an effort to help make understanding things a little easier for new SCCM Admins.

19.6.13

Запрос для определения 32 или 64 битной Win 7 для SCCM2012

http://ccmexec.com/2011/07/query-to-determine-32-or-64-bit-operating-system/

Query to find all Windows 7 – x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = "x64-based PC" and SMS_G_System_OPERATING_SYSTEM.Caption like "Microsoft Windows 7%"
And the query for Windows 7 -x86

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = "X86-based PC" and SMS_G_System_OPERATING_SYSTEM.Caption like "Microsoft Windows 7%"

7.6.13

Удаление OEM partition командой diskpart

Собственно, нужно удалить OEM раздел на Disk 1

1) Нажимаем окошко windows и клавишу R пишем cmd жмем Enter
2) Пишем diskpart жмем enter
3) Пишем list disk жмем enter
4) Выбираем нуный диск (если у вас два или более).. в нашем случае Disk 1, пишем  "select disk 1" жмем enter
5)Пишем, "list partition" жмем enter









6) Мой  partition 1 занимает 4769 мб.
7) Пишем "select partition 1" жмем enter
8) пишем "delete partition  override" жмем enter


5.6.13

Скачать полную exe версию Adobe Reader XI 11.0.03

Скачать полную exe версию Adobe Reader XI 11.0.03 
http://get.adobe.com/reader/enterprise/

расшифровка модулей Kingston DDR3

Расшифровка наименований модулей Kingston ValueRAM DDR3 HyperX DDR3

Как публиковать приложения в SCCM 2012

http://rorymon.com/blog/index.php/how-to-get-started-with-deploying-application-with-sccm-2012/



How to: Get Started with Deploying Application with SCCM 2012


Excuse the long title. I figured I should include the words Get Started in there to get across the point that, this is how you can simply deploy applications but it’s not necessarily the way you should. SCCM 2012 has even more capabilities and cool features than 2007. With that comes an even greater need for standardization. When implementing SCCM 2012 you should look at all it has to offer and decide what’s best for your environment. With the different options, comes a huge variety of way to do any one task, you need to define which one way is best for you and ensure everyone deploying applications in your environment knows it and follows that standard. The last thing you want to do is allow people to go rogue and deploy applications the way they see fit because it could and likely would lead to problems in the future which you may then have to remedy on some of your deployed applications. Nightmare situation! With that out of the way, here’s a couple of examples to get you started with testing out application deployments in SCCM 2012.
Example of SCCM Application Deployment
This blog post provides an example for pushing both an MSI application and also a Setup.exe with a custom parameter. This is not following any standard or best practice and is just an example of how to try it out. This also assumes you have completed your SCCM Setup and have collections to assign your applications to. For information on SCCM Setup try HERE
Before beginning you should be aware that there is two options. Create a Package or Create an Application. Applications have a lot more options e.g. can be based on requirements such as machine specs, it can also encapsulate dependencies and can also accept detection methods. If you used SCCM 2007 R2, a good way to think about this, is that this includes the advertisement in these steps. Where-as Packages are more like in-discriminant scripts to run on the client devices. They should not appear in the Software Center and should just execute on the end device when deployed.
Deploying a Setup.exe
For this example I pushed Microsoft Visio Professional 2010.
SetupExeStep1
First. You need to open the Configuration Manager Console
SetupExeStep2
When you are in there, you can click on Software Library
SetupExeStep3
Next expand Application Management and you should see Applications.
SetupExeStep4
Right Click on Applications and Click Create Application
SetupExeStep5
Click Manually specify the application information
SetupExeStep6
Enter in an appropriate name. Refer to the company standards. Enter the Manufacture name and also the Software Version. Click Next.
SetupExeStep7
Enter Keywords for the application and also browse to an appropriate icon. It’s a good idea to have the app installed on a machine so you can point to the main .exe to grab the icon. Click Next.
SetupExeStep8
Click Add to configure the Deployment Type here or just Click Next and you can do it later. Click Next.
SetupExeStep9
Click Next
SetupExeStep10
Click Close
SetupExeStep11
You can now browse to the application that you created. Right click and then click Create Deployment Type, if you did not already Add the Deployment Type.
SetupExeStep12
Select Script Installer (Native) from the list. Click Next.
SetupExeStep13
Follow company standards and add a name for your Deployment Type.
SetupExeStep14
Point your content location to the company standard Application folder where your setup.exe lives.
Point to your Setup.exe and configure the command you want to use. Browse to your Uninstall and configure the parameters. If your application is 32-bit you need to check “Run installation and uninstallation program as 32-bit process on 64-bit clients.” Click Next.
SetupExeStep15
Here you have a few different options. This detection method is used to tell if the app is already installed on the clients device and also tells the client if the installation completed successfully after installation. Above is looking for the main executable.
SetupExeStep16
Select Install for System from the dropdown for Installation Behavior. For this portion you may also want to resort to company standards. Maximum allowed run time defaults to 120 mins, you may want to change this.
SetupExeStep17
Here you can set requirements e.g. Only install if the client device has 4GB of RAM, 250GB free on the hard drive, is a member of the Laptops OU etc. Click Next
SetupExeStep18
If there’s dependencies you can add them here, if not Click Next
SetupExeStep19
Click Next
SetupExeStep20
Click Close
SetupExeStep21
Next go back to your application and click Distribute Content. This will push the installation files to the Distribution Group.
SetupExeStep22
Click Next
SetupExeStep23
Click Next
SetupExeStep24
Click Add and Click Distribution Point
SetupExeStep25
Click Next
SetupExeStep26
Click Next
SetupExeStep27
Click Close
SetupExeStep28
Go back to your application. Right click and then click on Deploy.
SetupExeStep29
Browse to the collection of devices you want to receive the application.
SetupExeStep30
Verify the Distribution Points and Click Next
SetupExeStep31
Here you can select if the application will be made available for the user to select to install it. With this option they can also Uninstall as they please. If you select Required it will get installed automatically and they will not be allowed to Uninstall through the Software Center.
SetupExeStep32
If you want to setup a schedule do it here. Click Next.
SetupExeStep33
Select if you want notifications to appear just for reboots or also for installations. Click Next.
SetupExeStep34
If you want to setup alerts and allow integration with SCOM you can set it here, I don’t want it right now so, Click Next
SetupExeStep35
Click Next
SetupExeStep36
Click Close
Deploying an MSI
The Distribute Content and Deploy sections from above still apply here. But the creating the Application part is slightly different. After you right click on Application and select to create an application.
MSISCCMStep1
This time you select Windows Installer (Native). Browse to the MSI on your company standard share. Click Next
MSISCCMStep2
Ensure the Name pulled from the MSI tables is ok. Also enter the Manufacturer and Software version if they don’t appear. If you have any transforms, ensure they are passed as a parameter in Installation program. If the application is 32-bit ensure to check the “Run installation program as a 32-bit process on 64-bit clients. Select Install for system (if this is the company standard) from the drop down and Click Next.
MSISCCMStep4
Click Close
MSISCCMStep5
You can now proceed to Distribute the Content and Deploy the application as per the earlier instructions above.
MSISCCMStep6
If you need to change something later you can do so by navigating to your application, navigating to the Deployment types tab on the bottom. Right clicking on the Deployment type and selecting properties. You will then see all of the possible options for your deployment. If you need to update the file contents you can make that change also. Right click again and select Update Content before proceeding to the next step.
Once your changes are made. You can now navigate to the Deployments tab, right click on the deployment and click Update Content. All changes should then be replicated across.
Refreshing the Client
MSISCCMStep7
You should see Configuration Manager in your Control Panel. Open it up and navigate to Actions.
MSISCCMStep8
You can run the check backs by selecting Run Now as you please.
MSISCCMStep9
You can then open Software Center on your client device
MSISCCMStep10
You should now see every application which is made available to you and choose to Install. You should also see the ‘required’ applications which should install automatically.