Windows · September 28, 2024
Windows Server 2003, while now considered outdated, was a popular choice for many organizations due to its stability and performance. However, as with any operating system, security is paramount. This article will explore safer methods for configuring security settings on Windows 2003 Server, providing technical examples to enhance your server’s security posture.
1. User Account Control
One of the first steps in securing a Windows 2003 Server is to manage user accounts effectively. By default, Windows 2003 allows users to have administrative privileges, which can lead to security vulnerabilities. To mitigate this risk, follow these steps:
- Create Standard User Accounts: Instead of using administrative accounts for daily tasks, create standard user accounts. This limits the potential damage from malware or accidental changes.
- Implement Group Policies: Use Group Policy Objects (GPOs) to enforce security settings across user accounts. For example, you can restrict access to certain system settings or applications.
Example: Creating a Standard User Account
net user username password /add
net localgroup "Users" username /add2. Firewall Configuration
Windows Server 2003 includes a built-in firewall that can be configured to enhance security. Properly configuring the firewall is essential to protect against unauthorized access.
- Enable the Windows Firewall: Ensure that the firewall is enabled and configured to block all incoming connections except those that are explicitly allowed.
- Configure Exceptions: Only allow necessary services through the firewall. For example, if you are running a web server, you may need to allow HTTP (port 80) and HTTPS (port 443).
Example: Configuring the Firewall
netsh firewall set opmode enable
netsh firewall add portopening TCP 80 "HTTP" ENABLE
netsh firewall add portopening TCP 443 "HTTPS" ENABLE3. Regular Updates and Patching
Keeping your server updated is crucial for security. Although Windows Server 2003 is no longer supported by Microsoft, it is essential to apply any available patches and updates that were released before the end of support.
- Enable Automatic Updates: Configure the server to check for updates regularly, ensuring that any critical patches are applied promptly.
- Monitor Security Bulletins: Stay informed about any vulnerabilities that may affect your server and apply patches as necessary.
Example: Enabling Automatic Updates
control /name Microsoft.WindowsUpdate4. Security Policies and Auditing
Implementing security policies and auditing is vital for monitoring and controlling access to the server. This can help identify potential security breaches and ensure compliance with organizational policies.
- Configure Security Policies: Use the Local Security Policy tool to set policies regarding password complexity, account lockout, and user rights assignments.
- Enable Auditing: Enable auditing for logon events, file access, and changes to user accounts to track any suspicious activity.
Example: Configuring Security Policies
secpol.msc5. Data Encryption
Data encryption is a critical aspect of securing sensitive information on your server. Windows Server 2003 supports Encrypting File System (EFS) for encrypting files and folders.
- Enable EFS: Use EFS to encrypt sensitive files and folders, ensuring that only authorized users can access them.
- Backup Encryption Keys: Always back up encryption keys to prevent data loss in case of user account changes or deletions.
Example: Encrypting a File
cipher /e filename.txtConclusion
Securing a Windows 2003 Server requires a multi-faceted approach, including user account management, firewall configuration, regular updates, security policies, and data encryption. By implementing these safer methods, you can significantly enhance the security of your server environment. For those looking to host their applications securely, consider exploring options like USA VPS Hosting to ensure a robust and secure infrastructure.
If you’ve ever deployed Windows NT Server or Windows 2000 Server, you probably know that Microsoft designed those products to be unsecure by default. Although Microsoft has provided many security mechanisms, it’s been up to you to implement them. But when Microsoft released Windows 2003 Server, the company switched philosophies. The new philosophy is that the server should be secure by default.
This is generally a good idea, but Microsoft didn’t take it quite far enough. While a default Windows 2003 installation is certainly more secure than a default Windows NT or Windows 2000 installation, it is still anything but totally secure. Let’s discuss some relatively easy measures that you can take to make Windows 2003 Server even more secure.
Know your role
Understanding the server’s role (i.e., intended purpose) is absolutely critical to the security process. There are many roles for which a Windows Server can be configured. For example, a Windows 2003 Server can act as a domain controller, a member server, an infrastructure server, a file server, a print server, an IIS Server, an IAS server, a terminal server, and the list goes on. A server can even be configured to fill a combination of roles.
The problem with this is that each server role has its own security needs. For example, if your server is going to function as an IIS server, you need to enable the IIS services. However, if the server is going to function solely as a file and print server, enabling IIS would be a huge security risk.
The reason I’m telling you this is to point out that there is no way that I can just give you a set of steps to follow and expect those steps to work in every situation. A server’s security needs vary tremendously by the server’s role and by the server’s environment.
Because there are many ways to harden a server, I’ll discuss the steps necessary for configuring a server to act as a simple, but secure, file server. I’ll try to point out some things that you might do differently if the server is filling an alternate role. Just please understand that this isn’t intended as a comprehensive guide to securing every type of server.
Physical security
To achieve true security, your server must be in a secure location. Normally, this means placing the server behind a locked door. Physical security is extremely important because many administrative and disaster recovery tools exist that can double as hacker tools. Anyone with such tools and a minimal skill level can hack a server in a matter of minutes once they have physical access to the machine. Your only hope against preventing such attacks is to place the server in a secure area. This is true of any Windows 2003 Server, regardless of its role.
Creating a baseline
Aside from establishing good physical security, the best advice that I can give you when deploying a series of Windows 2003 Servers is to decide on your security requirements prior to deployment and to enforce those policies immediately after deployment.
The best way to do this is to create a security baseline. A security baseline is a list of documented and accepted security settings. In most cases, your baseline settings will differ considerably depending on the server’s role. So the best thing to do is to create several different baselines that you can apply to various different types of servers. For example, you might have one baseline for file servers, another for domain controllers, and still another for IAS servers.
Windows 2003 contains a tool called the Security Configuration And Analysis Tool. This tool allows you to compare a server’s current security policy against a baseline security policy contained within a template file. You can either create these templates yourself or use one of the included template files.
The security templates are a series of text based INF files stored in the %SYSTEMROOT%\SECURITY|TEMPLATES folder. The easiest way to examine or modify the individual templates is through the Microsoft Management Console (MMC).
To open the console, enter the MMC command at the Run prompt. When the empty console loads, select the Add/Remove Snap-in command from the File menu. This will cause Windows to display the Add/Remove Snap-in properties sheet. Click the Add button found on the properties sheet’s Standalone tab and you will see a list of all of the available console snap-ins. Select the Security Templates snap-in from the list and then click the Add, Close, and OK buttons.
Once the Security Templates snap-in is loaded, you can view each of the security templates. As you navigate through the console tree, you will see that each template mimics the group policy structure. The template names reflect each template’s purpose. For example, the HISECDC template is a high security domain controller template.
If you’re trying to secure a file server, I recommend starting with the SECUREWS template. As you look through all of the template’s settings, you will find that although the template can be used to make the server more secure than it currently is, it may not meet your needs. Certain security settings may be too strict or too relaxed. I would recommend either modifying the existing settings to meet your needs or creating a brand new policy. You can easily create a new template by right-clicking on the C:\WINDOWS\Security\Templates folder within the console and selecting the New Template command from the resulting menu.
Once you have created a security template that meets your needs, go back to the Add/Remove Snap-in properties sheet and add a snap-in called Security Configuration And Analysis. When the snap-in loads, right-click on the Security Configuration And Analysis container, then select the Open Database command from the resulting menu. Since no database currently exists, make up a name for the security database. Click Open, and the necessary database will be created using the name that you provided.
Next, right-click on the Security Configuration And Analysis container and select the Import Template command from the shortcut menu. You’ll see a list of all of the available templates. Select the template that contains your security policy settings and click Open. After the template has been imported, right-click on the Security Configuration And Analysis container once again and select the Analyze Computer Now command from the shortcut menu. Windows will prompt you for a location to write the error log. Enter a file path and click OK.
At this point, Windows will compare your server’s existing security settings against those in the template file. You can see the results of the comparison by navigating through the Security Configuration And Analysis console. Each group policy setting displays both the current setting and the template setting.
Once you’ve had a chance to look through the list of discrepancies, it’s time to enforce the security policy based on the template. To do so, right-click on the Security Configuration And Analysis container one last time and select the Configure Computer Now command from the shortcut menu. The tool will then modify your computer’s security policy to match the template policy.
Group policies are hierarchical in nature. A group policy may be applied at the local computer level, the site level, the domain level, or the OU level. When you implement security based on a template, you’re modifying the computer-level group policy. Other group policies aren’t directly affected, although the final policy may reflect a change due to a setting in the computer policy being inherited by higher level policies.
Modifying built-in accounts
For years, Microsoft has been preaching that you need to rename the Administrator account and disable the Guest account to achieve good security. In Windows Server 2003, the Guest account is disabled by default, but renaming the Administrator account is still a good idea because it’s common for attackers to try to compromise the Administrator account.
There are a number of hacker tools that reveal the Administrator account’s real name by examining the account’s SID. Unfortunately, you can’t change this account’s SID and there is really no way of preventing such a tool from determining the Administrator account’s real name. Even so, I encourage everyone to rename the Administrator account and to change the account’s description for two reasons.
First, less sophisticated hackers may not know of the existence of such tools or have access to them. Second, renaming the Administrator’s account to a unique name makes it easy for you to monitor attacks against the account.
Another tip pertains to member servers. Member servers have their own built-in local administrative account that is completely separate from the domain Administrator account. You can configure every member server to use a different administrator account name and password. The idea is that if someone were to figure out the local administrator account name and password on one member server, you wouldn’t want them to be able to use those credentials to hack your other servers too. Of course, if you have good physical security in place, no one should be able to gain access to a server to be able to use a local account.
Service accounts
Windows Server 2003 is designed in a way that minimizes the need for service accounts. Even so, some third-party applications absolutely insist on a traditional service account. If possible, always use a local account as the service account instead of using a domain account, because if someone were to gain physical access to the server, they could dump the server’s LSA secrets, and compromise the password. If you use a domain password, the password can be used from any computer within the forest to gain access to the domain. If a local account is used, though, the password is useless from anywhere other than the compromised machine and doesn’t provide any access to the domain.
System services
There is a fundamental law of computing that states that the more code running on a system, the greater the chance that the code will contain a security vulnerability. One of the primary security strategies that you should focus on is to reduce the amount of code running on your server. Doing so reduces security risks and will also improve the server’s performance.
In Windows 2000, there were a lot of services that were running by default, but were totally unnecessary in most environments. In fact, a default installation of Windows 2000 even included a fully operational IIS server. In Windows Server 2003, Microsoft turned off most of the services that aren’t absolutely necessary. Even so, there are some services that are running by default, but are open to debate.
One such service is the Distributed File System (DFS) service. The DFS service was primarily designed to make a user’s life easier. DFS allows an administrator to create a logical name space containing resources from multiple servers or partitions. To a user, all of these distributed resources appear to exist within a single folder.
I personally like DFS, especially because of its fault tolerance and scalability features. However, if you were to not use DFS, you would force users to know the actual path to a specific resource instead of being able to access all resources through a single path. In some environments, this may translate to better security. In my opinion, though, the rewards of DFS far outweigh the risks.
Another such service is the File Replication Service (FRS). The FRS is used to replicate data between servers. This is a mandatory service on domain controllers because it’s responsible for keeping the SYSVOL folder synchronized. For member servers, however, this service isn’t mandatory unless you are running DFS.
If you have a file server that isn’t a domain controller and isn’t using DFS, I recommend disabling the FRS. Disabling the FRS decreases an attacker’s ability to replicate a malicious file across multiple servers. The FRS is enabled by default.
Another service worth taking a look at is the Print Spooler service. The Print Spooler manages all local and network print queues and controls all of the print jobs within these queues. The Print Spooler is required for all printing operations, and is enabled by default.
The flip side to this is that not every server requires printing capabilities. Unless a server is acting as a print server, you should disable the print spooler. After all, why should a dedicated file server run the print spooler? Normally, no one should be sitting at the server console working, so there should be no need to print locally or from across the network.
I realize that often during disaster recovery operations, it might become necessary to print an error message or an event log. However, I recommend simply turning on the Print Spooler Service when it is needed rather than leaving it on all the time for non-print servers.
Believe it or not, the Print Spooler is one of the most heavily exploited Windows components. There are countless Trojans that work by replacing the Print Spooler’s executable file. The reason for such an attack is that the Print Spooler operates as a system-level service and, therefore, has a high level of privileges. So any Trojan posing as the print spooler can also gain these high-level privileges. To protect your server from such an attack, just prevent the Print Spooler service from running.
TechRepublic originally published this article on 20 October 2003.
По кнопкам «Купить бумажную книгу» или «Купить электронную книгу» можно купить в официальных магазинах эту книгу, если она имеется в продаже, или похожую книгу. Результаты поиска формируются при помощи поисковых систем Яндекс и Google на основании названия и авторов книги.
Наш сайт не занимается продажей книг, этим занимаются вышеуказанные магазины. Мы лишь даем пользователям возможность найти эту или похожие книги в этих магазинах.
Список книг, которые предлагают магазины, можно увидеть перейдя на одну из страниц покупки, для этого надо нажать на одну из этих кнопок.
Секреты хакеров — Безопасность Windows Server 2003 — Готовые решения — 2004.
Эта книга станет настольным руководством для всех, кто хочет обеспечить безопасность систем под управлением Windows. Всемирно известные авторы расскажут читателям о мерах противодействия как классическим атакам на Windows-системы, так и о новейших средствах из арсенала современного хакера, предназначенных для взлома именно систем Windows Server 2003 На реальных примерах раскрыты нзвесгвые типы атак н рассмотрены наиболее приемлемые методы и средства противодействия каждой конкретной атаке, начиная от профилактических действий и заканчивая способами оперативного выявления вторжении
Книга рассчитана на сетевых администраторов и пользователей высокой квалификации
Авторы: Скембрей, Джоел, Мак-Клар, Стюарт.
Введение
ЧАСТЬ 1. ОСНОВЫ
Глава 1, Основы безопасности сетей и систем
Глава 2. Архитектура системы безопасности Windows Server 2003
ЧАСТЬ II. ПРОВЕДЕНИЕ АНАЛИЗА
Глава 3. Предварительный сбор данных и сканирование
Глава 4. Инвентаризация
ЧАСТЬ III. РАЗДЕЛЯЙ И ВЛАСТВУЙ
Глава 5. Атака на службы Windows
Глава 6. Расширение привилегий
Глава 7. Переход к интерактивноыу режиму работы
Глава 8. Расширение сферы влияния
Глава 9. Сокрытие следов
ЧАСТЬ IV. ИСПОЛЬЗОВАНИЕ УЯЗВИМЫХ СЛУЖБ И КЛИЕНТОВ
Глава 10. Хакинг сервера IIS
Глава 11. Хакинг сервера SQL
Глава 12. Хакинг программы Terminal Server
Глава 13. Хакинг Internet-клиентов Microsoft
Глава 14. физические атаки
Глава 15. Атаки отказа в обслуживании
ЧАСТЬ V. ЗАЩИТА
Глава 16. Возможности и средства защиты в системах Windows
Глава 17. Будущее безопасности Windows
ЧАСТЬ VI. ПРИЛОЖЕНИЯ
Приложение А. Перечень мер по защите Windows Server 2003
Приложение Б. О нашем Web-сайте поддержки
Предметный указатель
Бесплатно скачать электронную книгу в удобном формате, смотреть и читать:
Скачать книгу Секреты хакеров, Безопасность Windows Server 2003, Готовые решения — fileskachat.com, быстрое и бесплатное скачивание.
Скачать djvu
Ниже можно купить эту книгу, если она есть в продаже, и похожие книги по лучшей цене со скидкой с доставкой по всей России.Купить книги
Скачать книгу Секреты хакеров — Безопасность Windows Server 2003 — Готовые решения — depositfiles
Скачать книгу Секреты хакеров — Безопасность Windows Server 2003 — Готовые решения — letitbit
Дата публикации:
Теги:
программирование :: секреты хакеров :: Windows Server 2003 :: безопасность Windows Server 2003 :: готовые решения :: Скембрен :: Мак-Клар :: Стюарт :: атаки на службы Windows :: хакинг сервера SQL :: хакинг Internet-клиентов :: безопасность Windows :: книга :: скачать
Top Ten Tips for Security in Windows Server 2003
Guy’s top ten tips for Windows Server 2003 Security
Take as your mantra: ‘Preventions is better than cure’. It is more fun configuring the system to prevent security breaches than implementing disaster recovery plans.
1) Administrators Account – Needs Renaming
If hackers do not know the name, then they cannot start guessing the password. Choose a name which blends in with the other users. You could even create a dummy Administrator account with no rights. Audit the account and see what happens.
Master the Security Configuration and Analysis Snap-in
Use the Templates to check the available security settings for different levels of security e.g. HISECDC – High security settings for a domain controller.
Guy Recommends 3 Free Active Directory Tools
SolarWinds have produced three Active Directory add-ons. These free utilities have been approved by Microsoft, and will help to manage your domain by:
- Seeking and zapping unwanted user accounts.
- Finding inactive computers.
- Bulk-importing new users. Give this AD utility a try, it’s free!
Download your FREE Active Directory administration tools.
2) Certificates
Take the time to check out the variety of roles where certificates can improve security, examples: EFS, L2TP, and email. Develop a policy and a strategy for certificates, for example set up your Active Directory certificate authority to be a subordinate of VeriSign.
3) Check the Security Logs
It is no use having a marvellous security system if you do not check to see what is happening. Get to know the significant Security events such as ID’s 675 and 680.
4) EFS on Laptops
Equip your laptops with EFS, this will prevent people stealing the files through a parallel installation. However it will not provide protection if the thief can guess the user’s password. If you do you EFS take the time to practice with the recovery agent. You will find that you have to backup the data and restore it on the server with the recovery agent’s certificate.
5) Make the Run As command your friend
Always logon with your ordinary humble account, and when you want administrative privileges, instead of logging off – which is a pain – use Run As. You can even modify shortcuts to Run As another user.
6) L2TP for your VPN’s not PPTP
It seems that PPTP is a favourite choice for hackers, so configure the clients to use L2TP. However the certificates are awkward to set up, so take care with the instructions.
7) Lockup your Root Servers
Do not neglect physical security, particularly for the servers in your root domain. Think of the disaster if there was only one root server and it was stolen.
Services that you do not use?
Services that you do not use?If there are any services that you are not using, then make sure they are disabled. Do you need IIS, FTP or Telnet on the server? Should clients run VB or java scripting engines or macros?
9) User education
User support and acceptance for your security initiatives will be your unseen friend. Foster goodwill by explaining why account security is so important. Reinforce the message with horror stories from other companies.
10) Which service packs do you have?
Back to basics, remember to check for the latest security hot-fixes. Several of these hot-fixes have prevented virus attacks which have crippled competitors.
Guy’s Challenge – Download this free device backup utility
(CatTools)
Kiwi CatTools is a free program for backing up configuration settings on hardware devices. Here is Guy’s challenge. If you download CatTools, then it will not only take care of backups, but also it will show you something new about the hardware on you network. I could give you a money back guarantee – but CatTools is already free! Thus, I just make a techie to techie challenge, you will learn more about your network if you:
Download your free Kiwi CatTools configuration backup tools
If you like this page then please share it with your friends
Related topics
• Accounts • Auditing • IPSec • Kerberos Tickets • Windows RIS Server
•LT2P and Certificates • Security Snap-in • Remote Shutdown
About The Author
Guy Thomas
|
|
|
|
Лучшее в категории — Книги / Компьютерная литература
| Windows 10 для чайников (2016, Энди Ратбон) Рейтинг: 10 из 10 |
Смартфоны и планшеты Android проще простого (2015, Евгения Пастернак) Рейтинг: 9,5 из 10 |
Бизнес-анализ с использованием Excel. 4-е издание + CD (2014, Конрад Карлберг) Рейтинг: 9,5 из 10 |
Программирование на Python для начинающих (2015, Майк МакГрат) Рейтинг: 9,4 из 10 |
Программирование. Принципы и практика с использованием C++. 2-е издание (2016, Бьярне Страуструп) Рейтинг: 9,4 из 10 |
Сборник книг по программированию на С и С++ (1992) Рейтинг: 9,3 из 10 |
Windows 10. Новейший самоучитель (2015, Виталий Леонтьев) Рейтинг: 9,3 из 10 |
Язык программирования C. Лекции и упражнения. 6-е издание (2015, Стивен Прата) Рейтинг: 9,3 из 10 |
27
июн
2015
Excel — готовые решения (2014, Николай Павлов)
Эта книга представляет собой полноценный сборник готовых решений самых распространенных проблем и задач, с которыми сталкиваются в повседневной работе пользователи Microsoft Excel. Материал книги охватывает все основные направления и темы: работу с текстом и датами, форматирование, вычисления с помощью формул и функций, обработку больших …
ISBN: 978-5-519-01837-1
Формат: PDF, EBook (изначально компьютерное)
Автор: Николай Павлов
Год выпуска: 2014
Жанр: Компьютерная литература
Издательство: Книга по Требованию
Язык: Русский
Количество страниц: 382
03
янв
2014
Microsoft Windows Server 2012. Полное руководство (2013, Рэнд Моримото)
Microsoft Windows Server 2012. Полное руководство — Книга представляет собой наиболее полное руководство по планированию, проектированию, прототипированию, реализации, переносу, администрированию и сопровождению Windows Server 2012. В значительной мере переработанная, она содержит непревзойденное независимое и объективное изложение основн …
ISBN: 978-5-8459-1848-2
Формат: PDF, DjVu, OCR без ошибок
Автор: Рэнд Моримото, Майкл Ноэл, Гай Ярдени, Омар Драуби, Эндрю Аббат, Крис Амарис
Переводчик: А. Моргунов
Год выпуска: 2013
Жанр: Компьютерная литература, программирование
Издательство: Вильямс
Серия: Полное руководство
Язык: Русский
Количество страниц: 1456
15
фев
2012
Microsoft Windows Server 2008 R2. Полное руководство (2011, Рэнд Моримото)
Эта книга представляет собой исчерпывающий и основанный на богатом опыте авторов учебник по планированию, проектированию, прототипированию, внедрению, миграции, администрированию и поддержке систем на базе Windows Server 2008 R2. Рэнд Моримото (Microsoft MVP) вместе со своими коллегами предлагает профессионалам в области информационных те …
ISBN: 978-5-8459-1653-2, 978-0-672-33092-6
Формат: DjVu, Отсканированные страницы
Автор: Рэнд Моримото, Майкл Ноэл, Омар Драуби, Росс Мистри, Крис Амарис
Год выпуска: 2011
Жанр: Компьютерная литература
Издательство: Вильямс
Язык: Русский
Количество страниц: 1457
07
авг
2014
Секреты, настройка и оптимизация реестра Windows 7 (2010, Денис Колисниченко)
Рассмотрено устройство, настройка и оптимизация реестра, секреты и трюки при работе с ним, параметры популярных Windows-приложений. Описаны программы для мониторинга, чистки и быстрой настройки реестра, которые пригодятся каждому пользователю. Для администраторов систем даны приемы управления реестром (политики, списки доступа), использов …
ISBN: 978-5-9775-0488-1
Формат: PDF, EBook (изначально компьютерное)
Автор: Денис Колисниченко
Год выпуска: 2010
Жанр: Компьютерная литература
Издательство: БХВ-Петербург
Язык: Русский
Количество страниц: 320
09
сен
2010
Защити свой компьютер на 100% от вирусов и хакеров (2009)
Добро пожаловать! Наверняка читатель, который держит в руках эту книгу, уже не понаслышке знаком с вопросами информационной безопасности вообще и компьютерной в частности. Даже если это не так и вы начинающий пользователь, то материал, приведенный в книге, должен помочь продвинуться вглубь. «Выше, быстрее, сильнее!» – именно этот девиз до …
Формат: PDF, EBook (изначально компьютерное)
Год выпуска: 2009
Жанр: Компьютеры, безопасность, защита против хакеров
Язык: русский
Количество страниц: 176
07
мая
2011
Репликация SQL Server 2005/2008. Сборник статей от сообщества SQL.RU
Эта книга — сборник статей, которые посвящены ключевым для понимания репликации SQL Server моментам. Кроме переводов наиболее интересных зарубежных авторов, являющимисяхся признанными во всём мире специалистами, в книге вы найдёте ряд статей участников сообщества SQL.RU, которые многие годы помогаю решать разнообразные проблемы на техниче …
ISBN: 978-5-9790-0086-2
Формат: PDF, EBook (изначально компьютерное)
Автор: А. Гладченко и В. Щербинин
Год выпуска: 2008
Жанр: Компьютерная литература
Издательство: ЭКОМ
Язык: Русский
Количество страниц: 284
04
июн
2008
Windows. Народные советы (2006, Александр Климов)
Учебно-практическое пособие; Рассмотрены скрытые возможности операционной системы Windows, не описанные в документации, которые существенно расширяют ее функциональность, делая вашу работу за компьютером более комфортной, стабильной, производительной и увлекательной. Представлены малоизвестные программы и утилиты, входящие в состав Window …
Автор: Александр Климов
Издательство: БХВ-Петербург
Год выпуска: 2006
Количество страниц: 225
28
мая
2008
Реестр Windows XP (2003, Джерри Хонейкатт)
Умение работать с реестром позволит вам настроить Windows XP так, как вы не сможете настроить ее с помощью интерфейса пользователя. Вы узнаете, куда в реестре Windows XP и другие программы сохраняют свои настройки, научитесь создавать и распространять эффективные профили пользователей, писать скрипты для редактирования реестра, создавать …
Автор: Джерри Хонейкатт
Издательство: Эком
Язык: Русский
Год выпуска: 2003
Количество страниц: 655
02
окт
2008
1000 Секретов Windows (2008)
В данном архиве материалы которые помогут новичку (да и нетолько) раобраться в ОС WINDOWS. Как оптимизировать систему, разобраться с настройкой реестра. NTFS и FAT, Администрирование дисков, Установка и восстановление WinXP с нуля, и многое другое. Метериалы представленны в текстовом виде, формат: Документ Microsoft Office Word 97 — 2003
Формат: Обычный текст, EBook (изначально компьютерное)
Год выпуска: 2008
Жанр: Компьютерная Литература