Skip to main content

Posts

Showing posts with the label Windows

How do I create a MSI wrapper over EXE installation files?

In order to exemplify the procedure, we will assume to wrap three .EXE installers "test1.exe", "test2.exe" and "test3.exe" into a .MSI. Here are the steps: 1. In Product Details Tab (Product Details Page) under "Add or Remove Programs (Control Panel)" group, uncheck the "Register product with Windows Installer" option. We don't want the wrapper to appear in "Control Panel" -> "Add or Remove Programs" as an installed program. 2. Go to Files and Folders Page and add the .EXE installers in the "Application Folder". 3. Create a .BAT file with the following content and add it in the Files and Folders Page: "|InstallPath|test1.exe" "|InstallPath|test2.exe" "|InstallPath|test3.exe" 5.  In the same folder, using the toolbar or context menu, create a text file update for the .BAT file. This file update should include a single replace operation: Find : |InstallPath|

How to deploy a MSI on multiple machines by using Group Policy.

1. Methods of deployment Group Policy supports two methods of deploying a MSI package: Assign software - A program can be assigned per-user or per-machine. If its assigned per-user, it will be installed when the user logs on. However, if its assigned per-machine then the program will be installed for all users when the machine starts. Publish software - A program can be published for one or more users. This program will be added to the Add or Remove Programs list and the user will be able to install it from there. 2. Create a distribution point The first step in deploying a MSI through GPO is to create a distribution point on the publishing server. This can be done by following these steps: A.log on to the server as an Administrator user B. create a shared network folder (this folder will contain the MSI package) C. set permissions on this folder in order to allow access to the distribution package D. copy the MSI in the shared folder E. In the shared folder you can al

Cleaning up Deleted Items Automatically from Exchange

You can use Mailbox Manager to create a recipient policy to automatically delete all messages from users Deleted Items folder, at an interval you specify. To create a policy to delete forwarded messages Open Exchange System Manager in the Exchange organization in which the journaling mailbox resides. Expand the Recipients folder. Right-click the Recipient Policies folder, point to New, and then click Recipient Policy. In the New Policy dialog box, select Mailbox Manager Settings, and then click OK. In the Properties dialog box, on the General tab, do the following: a. In the Name box, enter a policy name. b. Under Filter rules, click Modify. In the Find Exchange Recipients box, create a search query that will return all your users or certain users/mail boxes you want affected. When you finish building the query, click OK. In the message that appears, click OK. Click the Mailbox Manager Settings (Policy) tab, and then do the following: a. In the When processing a mailbox dro

How long are deleted items retained? How do I configure automatic permanent deletion?

How long deleted items are retained depends on the type of account and how it is configured. For  IMAP  accounts, you can edit the account settings to automatically delete after a certain interval or you can use the Schedules tool to schedule automatic deletes For  Exchange  accounts you can use the Schedules tool to schedule automatic deletes For  POP  accounts, you can edit the account settings or use the Schedules tool to schedule automatic deletes IMAP - to schedule automatic permanent deletion of items in your Deleted Items folder in an IMAP account you may do one of the following: Edit account settings Go to Tools > Accounts Select the Mail tab, highlight your IMAP account, and click Edit Under the Edit Account menu, click the Advanced tab Under Delete options choose how you would like your messages to be deleted Use Schedules Go to Tools > Run Schedule > Edit Schedules Name the schedule For "When," choose something other than manual and configure,

Howto: Backup IIS 7.0 web server configuration

To backup your IIS 7.0 configuration on a Windows 2008 Server, you just need to make a copy of the \windows\system32\inetsrv\config  directory (and subdirectories) and save it in a safe location. You can also use the appcmd.exe utility to create the backup via the command line. The syntax to create a backup is: %windir%\system32\inetsrv\appcmd.exe add backup “Backup Name” to restore the backup, the syntax is: %windir%\system32\inetsrv\appcmd.exe restore backup “Backup Name” to remove a backup, the syntax is: %windir%\system32\inetsrv\appcmd.exe delete backup “Backup Name”

Howto: Configure the Windows 2008 Server Core Screensaver Activation Period

By default the Windows 2008 Server Core screensaver will activate after 600 seconds (10 minutes) of inactivity. To change the amount of time the screensaver waits to activate, edit the following registry key: HKEY_CURRENT_USER\Control Panel\Desktop\ScreenSaveTimeOut I changed mine from 600 seconds (10 minutes) to 1200 seconds (20 minutes).

How to completely disable DEP in Windows Server 2003

To completely disable DEP in Windows Server 2003, perform the following with administrative credentials: 1. Open Windows Explorer 2.  Tools > Folder Options > View 3. Uncheck  Hide Protected operating system files (Recommended)  and  Hide extensions for known file types 4. Click apply > OK 5. Browse to C:\ 6. Right click on boot.ini, select properties and ensure the “read-only” tab is  unchecked  and click OK 7. Edit boot.ini 8. Modify the   /noexecute= For example, set   /noexecute=AlwaysOff  to disasble DEP entirely 9.  File > Save , close boot.ini file 10. Right click on boot.ini, select properties and ensure the “read-only” tab is  checked  and click OK 11. Reboot the computer For more about DEP see MS  KB875352   

Windows Server 2008 R2 : File Server Resource Manager Installing the File Server Resource Manager Tools & FSRM Global Options

Windows Server 2008 R2 includes a file system management and reporting configuration tool named the File Server Resource Manager (FSRM). This service and tool was first introduced in Windows Server 2003 R2 and provides administrators with the ability to configure quota management at the volume and folder level, create and apply file screening policies, generate alert notifications and reports on a schedule and in real time, and classify files and folders based on administratively defined criteria. With the volume-level quota management, previously included with Windows Server versions, administrators were very limited on how quotas could be applied and several issues were encountered. Many organizations that required tighter control of their storage were forced to utilize third-party quota management software to get the functionality they required. With the quota management functionality included with the FSRM service in Windows Server 2008 R2, administrators can now create quotas at

TCP/IP: DNS, WINS, & DHCP

DNS and WINS are really for doing two different (but similar) things. Second, each has been co-opted to assist the other in some cases -- and as a last resort. Literally  Domain Naming System (DNS) servers, resolve Domain Naming System names to IP addresses.  Sounds redundant, but technically it is almost literally true (not quite for you advanced people) that an IP host has NO NAME; it has a DNS name only by virtue of the DNS servers or by convention. Windows Internet Naming Services (WINS) servers resolve NetBIOS names to IP addresses . NetBIOS names ARE a feature of the network node (or host machine). The NetBIOS protocols require that NetBIOS nodes 'defend' their name from other machines attempting to use the same name. Likewise,  a 'host' file resolves DNS names to IP addresses  while  an 'LMHOST' file resolves NetBIOS names to IP addresses. So you can see a 1-1 mapping of DNS server to host file, and WINS server to LMHOSTS file. The order of use of these

How To Install and Configure a File and Print Server in Windows Server 2003

Install File and Printer Sharing By default, a Windows Server 2003-based computer is installed with Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and TCP/IP. NOTE : You can view these services in the properties for the local area connection. You can create a Windows Server 2003 file server and print server manually, or you can use the wizards that are provided in the Configure Your Server Wizard administrative tool. How to Install a File Server on Windows Server 2003 by Using the Configure Your Server Wizard Click  Start , point to  Administrative Tools , and then click  Configure Your Server Wizard . Click  Next . Click  Next . Click  File server  in the  Server role  box, and then click  Next . On the "File Server Disk Quotas" page, configure any quotas you need to control disk-space usage on the server, and then click  Next . On the "File Server Indexing Service" page, click the indexing configuration that is appropriate fo