Author Archives: Alon yardeni

About Alon yardeni

Information Technology specialist, Media & Video specialist, SEO.

Follow Gmalaya on Google+

How to set spacing in Outlook for new and reply emails

Facebookgoogle_plus

set spacing in Outlook for new and reply emails will help users to define one time the spacing style.Office 2010 and office 2013 this process done one time for new emails and one time for reply emails. After configuring it one time – office will keep the configuration until the next change.

Set spacing for new emails:

1. Open new message in outlook client.
2. Go to “format text” < select “change style”. (You can also use “line and paragraph spacing” but it will change only one time). 3. Drop down the right ribbon to set the wished style. 4. Close the new message window. 5. Open new message window to check spacing after the change. For reply emails you may do exactly the same with one change, in section 1, do not open a new message, and instead reply to any email you have in your mailbox to set the exact configuration.

exchange 2010 no-reply email

Facebookgoogle_plus

Creating an exchange 2010 no-reply email can be done in few easy steps that basically includes group with authorized users to send email as no-reply@domain-name and on the other hand block emails sent to no-reply@domain-name email address.
Follow this procedure to create an Exchange 2010 no-reply email:
Step 1 (allow outgoing no-reply email for users)
1.Open active directory users and computers snap in.

2.Create a new users and name it “No-Reply” < create a password for that user < mark the “user cannot change password” and “password never expired” fields.

3.Open exchange 2010 console < add mailbox for existing users < create mailbox for no-reply user.

4.If you want to let number of users send email as no-reply < open active directory users and computers snap in < open a new Global |Security group < add all the users that need permission to send as no-reply to this group.

5.Open No-Reply user properties < go to security tab < add the group you created on section 4 < mark the “send as” permission for this group.

Step 2 (disable incoming messages to no-reply mailbox:

1.Open exchange 2010 console.

2.Go to transport rules < create a new transport rule (this step is much similar to creating an outlook rule except it’s a server rule).

3.Under “conditions” < Mark the upper tab called “send to people” < on the bottom choose the no-reply mail address < press “next”.

4.Under “actions” < mark the Send rejection message to sender with enhanced status code” and edit the message you want to be appear to people that sent to no-reply.

That’s is
Now you can send as a logged in user from the no-reply group.

Personalize Symantec endpoint protection client install

Facebookgoogle_plus

Symantec endpoint protection solution involves Personalize Symantec client install for be managed under the requested client group.
This can be achieved using a client install process which divided to 3 sub processes:
1. Client install package.
2. Client install settings.
3. Client install feature set.

To prepare Symantec endpoint protection client installations do the follow:

1. Open Symantec endpoint protection manager.
2. On the left pane < Go to “admin” < “install packages”
3. On bottom left pane point to “client install package”.
In default, Symantec endpoint protection comes out of the box with three main client installs: windows 32 bit, windows 64 bit and MAC.

To add additional client install:

1. Right click the white area in right pane (where you see the other 3 clients).
2. Click “add”.
3. Specify a name for the package.
4. Specify the source folder.
5. Click “ok” < the engine will now compile a new package for deployment.

To prepare Symantec endpoint protection client install settings do the follow:

1. Open Symantec endpoint protection manager.
2. On the left pane < Go to “admin” < “install packages”
3. On bottom left pane point to “client install settings”.
4. Right click the white area in right pane.
5. Click “add”
6. Give a name to the client install configuration.
7. Recommended to change configuration only if necessary, keep in mind that for deploying new client
It’s recommended to mark on the last section the option “remove all previous logs and policies”.
To prepare Symantec endpoint protection client install feature set do the follow:
1. Open Symantec endpoint protection manager.
2. On the left pane < Go to “admin” < “install packages”
3. On bottom left pane point to “client install settings”.
4. Right click the white area in right pane.
5. Click “add”.
6. Give a name to the client install feature set.
7. Mark and unmark features according to organization needs.
To preform client install process do the follow:

1. Open Symantec endpoint protection manager.
2. On the left pane < Go to “clients” < make sure you point to the requested group on the “clients” tree.
3. on the left pane click “add a client”.
4. Select “new package deployment” < Press next < choose the requested package < choose the requested feature set <
Choose the requested settings < choose “Basic” in the content options tab < press next.
5. Select the “remote push” option < press next.
6. Find the requested station using domain name or IP address and deploy the client.
7. The client should be installed in station, reboot and mark with green small rectangle that indicates that the client is now managed by Symantec endpoint protection server.

Outlook 2013 crash configuring exchange account

Facebookgoogle_plus

One of the most familiar issues with outlook 2013 undated version is the outlook 2013 crash when configuring exchange account, IMAP account or POP account using windows 8.1 operating system.
Many of the articles on that issue relate to basic crash “”Microsoft Outlook has stopped working. Microsoft is looking for a solution.” when trying to open the program, each case with a different DLL name and different annoying 0xc000000 fault in event viewer.
From my experience, try the following items before re-installing\installing office 2013 and update it.
1. Disable your antivirus program and open outlook.

2. Disable all unnecessary add-ins as follow:
Open outlook 2013 > go to “file” > go to “options” > go to “add-ins” > below locate the “Manage” criteria > Press “GO” > Uncheck the add-ins that not related directly to office 2013.

3. Disable exchange cache mode and test if outlook opens.

4. Update office 2013 with the latest updates: last update available to outlook writing this article can be found here.

Setup AD FS and Enable Single Sign On to Office 365

Facebookgoogle_plus

Microsoft Office 365 cloud solution is a set of tools designed to propose full or partial Active directory, office 2013 application, Lync and SharePoint.
Full Office365 solution much known as Azure, but in this article we’ll deal with Setting up AD FS and Enable Single Sign On to Office 365, which is basically installing local Active directory and connect it to Office 365 cloud mail solution using Single Sign On. The main idea for using Single Sign On is to replicate passwords so user will not have to deal with two separate passwords for AD and for Office365. The following process will show How to Setup AD FS and Enable Single Sign On to Office 365.

Setup AD FS
1. Install AD FS Server role in Active directory server.
2. Install IIS in AD FS server.
3. Install Active Directory Sync Tool in a separate server in domain (not active directory server).
4. In case you are using internal domain name that doesn’t match the domain name need to be federated with Office 365, add a custom UPN suffix that matches that external name as follow:
a. Open Active Directory Domains and Trusts.
b. Go To “Tree” window pane < Right-click “Active Directory Domains and Trusts” < click “Properties”.
c. Under the “UPN Suffixes” tab, type the new requested UPN suffix.
d. Click “Add” < click “OK”.
e. Set up all requested users in AD with the new UPN (you may do it by multi checking all users in any OU and change the “User logon name” under account properties.

Enable Single Sign On to Office 365.

5. Setup up AD FS third party SSL certificate as follow:
a. Open Server Manager < click “tools” < choose “Internet Information Services (IIS) Manager”.
b. Go to “local server” < Select “Server Certificates” < Click Open Feature < Click “Create           Certificate Request”.
c. Fill certificate request using the format name “sts.domain.com”. For example: if you want to create certificate for domain JangoNet.com use certificate request “STS. JangoNet.com”.
d. Fill in all other details < click “next” < set “Cryptographic service provider” as default < Change the “Bit Length” to 2048 < Select a file location for the request < click “finish”.
e. But a standard certificate from one of the domain registrations companies like Go Daddy. Please be sure to but standard certificate and not wildcard certificate as wildcard will not propagate the request in IIS in windows 2012 servers.

6. Complete the certificate request in IIS as follow:
a. Go to “Internet Information Services (IIS) Manager” < select “local server” < select “Server Certificates” < Click “Open Feature” .
b. Click “Complete Certificate Request” < Select the path to certificate that downloaded from provider in section 5e < Enter a “friendly name” for the certificate < Select “Personal” at the certificate store < see the added certificate under “server certificates”.

7. bind the default website to the server certificate as follow:
a. Go to IIS < Expand “Sites” < Select Default Web Site < Click Bindings < click “add” < Change the type to HTTPS.
b. Select the site certificate from the list <click “OK”.

8. Configure Local AD FS Federation Server as follow:
a. Go to ” Server Manager” < ” Tools” < choose ” AD FS Management” < click ” AD FS Federation Server Configuration Wizard”
b. Check “Create a new Federation Service”
c. Check “New Federation Server Farm” < click “next”.
d. The “SSL Certificate” should be choosing already.
e. In “Federation Service Name” choose the certificate from list.
f. Click “next” < enter the “AD FS service account” name and password.
g. Click “next” <see all process marked with green V < click “close”.

9. Set the active directory email address settings for users in Office 365 as follow:
a. Open active directory users and computers.
b. Right click user < click “properties”.
c. Click “attribute editor” on the bottom pane.
d. Seek for ” ProxyAddress” field.
e. Add the requested mailbox address like this < for the default mail address enter: SMTP:user@domain.com for example: SMTP:jonathan@jangonet.com .
f. Add as many aliases as you want with “smtp” small letters like: smtp:jona@jangonet.com.

10. Check federation connectivity works as follow:
a. User Active directory sync tool on another server in domain to sync local Active directory users to Office365 cloud. This tool is very easy and all you should do is put the Office 365 admin user and password, local active directory user and password, mark “sync passwords” and make sync. After the sync you should see users in Office 365 marked with “AD synced user”.
b. Change password for one of the users in local Active directory and after 10 minutes to login to Office365 with new user password. That will indicate that the password replicated to cloud.
c. In Office365 cloud < under exchange settings < check users got the current default SMTP address and alternative smtp address to ensure “Proxyaddress” field replicated to cloud.

MDT 2012 network error during boot

Facebookgoogle_plus

MDT 2012 network error during boot is a phenomena when trying to boot a computer using the MDT 2012 ISO file created, the network driver for than machine can not be loaded due to the fact that the windows PE created by MDT 2012 doesn’t have the proper driver.

You may get error like:
The following networking device did not have a driver installed.
PCI\VEN_15AD&DEV_0789&SUBSYS_07B345AD&REV_01

The solution for is as follow:

  1. Download the network card drivers from the manufacture site (in most cases this driver is an EXE file which you should extract to a directory).
  2. Go to the MDT 2012 console < open the “Deployment share” you created.
  3. Right click “out of the box driver” < add new drivers < browse for the directory you extracted the drivers to < finish process.
  4. Now you should see the additional network drivers under “out of the box driver”.
  5. Right click your “Deployment share” < choose “update deployment share” – this will recreate the bootable ISO for booting your computer with appropriate network drivers this time.

Deploy windows and office with MDT 2010

Facebookgoogle_plus

Deploy windows and office with MDT 2010 is the quickest, easiest and protected way to deploy automated install of windows 7 or windows 8 workstations with office 2003, office 2007 or office 2010 applications for entire organization.
Microsoft Deployment toolkit is a program that can be install on windows workstation or server. During writing this article the updated version is Microsoft Deployment toolkit 2010 update 1. In order to deploy windows and office with MDT 2010 there are some prerequisites we should install first to allow clean and fast working with Microsoft Deployment toolkit:

  1. .Net framework version 2.0 service pack 2 or older (if installing Microsoft Deployment toolkit on server this is a server role needed to be add to server).
  2. Windows automated installation for windows 7.
  3. Windows 7 or windows 8 operation system files (with available MAK or KMS serial numbers for activation).
  4. Office 2003 or office 2007 or office 2010 files (again with appropriate serial key).

Be sure to have a spare logical or physical drive to work in for that matter.

We’ll split the procedure to few sub procedures to make life easier.

Prepare MDT 2010 installation files and prerequisites:

  1. Install software below from section 1-4.
  2. Create on spare drive with approximately 50GB free the following folders:Windows OS, Office Application.
  3. Copy the windows 7 or windows 8 files to “Windows OS” folder.
  4. Copy the office application files to “Office Application” folder.
  5. Open the “Deployment workbench” application < right click “deployment shares” and choose “new deployment share”.
  6. Name the share, fill in the description, mark the “ask if an image should be captured” and walk through the end of process.
  7. Check the share availability by clicking the “Start” < run < \\ServerName\Sharename
  8. Under “deployment shares” < open the Deployment share name you created.

Create operation system files

  1. Right click “operating systems” < choose the “import operation system” option.
  2. Choose “full set of source files”.
  3. Browse to the windows source folder contains the source files you prepared on section 3.
  4. Select the “move the files to deployment share to make the process faster.
  5. Finish the process < check on the Windows OS folder to see that all files transferred.

 Create application files

  1. Right click “operating systems” < choose the “applications” option.
  2. Choose “new application”.
  3. Fill in publisher, application name and version
  4. Browse to the Office Application folder contains the source files you prepared on section 4.
  5. Set the startup command file to “setup.exe”.
  6. Finish the process < check on the Office Application folder to see that all files transferred.

 Create task sequence

  1. Right click “task sequence” < choose the “new task sequence” option.
  2. Fill in the task sequence ID, name and comments if you have.
  3. Leave the template as standard.
  4. Select the OS < fill in the KMS license key < set admin password for automated task< finish the process.

Update deployment share

  1. Go to ” deployment share name” you created < right click and choose ” update deployment share”
  2. Finish the process while make sure all WIM and ISO files created under the spare logical or physical drive \ deployment share name you created.
  3. Burn the ISO file (bootable) to CD and use it to start stations with automated windows and office install on the network.

nstallation for workstations without network

For those computers excluded from network or have no network card or network port available you should create a separate media which will be larger than the network boot media since it contains all windows and office installations inside.

To deploy windows and office with MDT 2010 to computers with no network access:

  1. Create a folder under the logical drive (for ex: E:).
  2. Open the “Deployment workbench” application < right click “deployment shares” and choose “advanced configurations” < right click “Media” < choose “new Media” < name it “WinLocal”
  3. On “media Path” browse to folder you created on section 1 <finish the process.
  4. Right click the “WinLocal” < click “Update media content” < the process will copy all media content to local “media” folder on logical drive and create a ISO file that can be burned and use for workstations without network.

Configuration

You can always change configuration for task sequence, applications and operation systems by right click the item < choose “properties” and change running platform, enable and disable task and edit XML configuration depending on the item.

Unable to install .net 3.5 on windows 8

Facebookgoogle_plus

When Unable to install .net 3.5 on windows 8 even after running the appropriate command using dism.exe to enable net 3.5 and getting the “access denied” error running:

dism.exe /online /enable-feature /featurename:NetFX3 /Source:d:\sources\sxs /LimitAccess

to solve this just Start <run < all programs  < accessories < command prompt (right click) < choose “run as administrator” < run the dism.exe command again.

Windows 2008 server SMTP

Facebookgoogle_plus

Windows 2008 server SMTP service allows taking advantage of SMTP abilities to monitor hardware and software activity in order to be updated about any service or error on server.
The most important configuration Windows 2008 server SMTP service needs to run is open relay for server and appropriate firewall ports open.
Testing Windows 2008 server SMTP service can be done using the windows telnet command to port 25.

In order to configure Windows 2008 server SMTP service:

  1. Add SMTP features on server under “add feature wizard” .
  2. Add IIS web services console and tools.
  3. Open IIS under “administrative tools”.
  4. Browse to SMTP virtual server box.
  5. Right click on server name in IIS and choose “Add new SMTP virtual server”.
  6. Name the new SMTP virtual server.
  7. Choose the IP in which the virtual server uses for service SMTP requests.
  8. Select home directory.
  9. Fill in the domain name that will hold the SMTP server.
  10. Click “finish”
  11. Go to new SMTP server on left pane < right click “properties”.
  12. Check the “limit connection to” and choose some reasonable connection number (30).
  13. Go to “access” tab < press “authentication” < uncheck “anonymous access” < check the “basic authentication” and “Require TLS encryption” < fill in the domain name < press ok or uncheck all and check “windows based authentication”.
  14. Go to “connection control” < click “connection” button < grant access only to local server IP.
  15. Click the “relay” button < check the “grant access to list below” < add you domain name for accessing this virtual server.
  16. Go to “delivery” < check the “outbound security” button < check the “integrated windows authentication” and fill in admin user and password.

You may limit outbound connection under “outbound connection”.

IE10 unable to download files

Facebookgoogle_plus

When IE10 unable to download files and comes up with drop down tab indication the error “select list not active in editor mode” :

Remove IE10 from add-remove programs.

Make sure security option marked to “Off” or lower security level.