Archive for category windows 7

Deploy Pervasive SQL v10 SP3 Using SCCM 2012

Here are the steps to deploy Pervasive SQL v10 SP3 client to your Windows 7 machines using Microsoft’s SCCM 2012.

  1. Create an application package, and you’re going to use SetupWorkgroup_x86.exe
  2. Use the following installation parameters: SetupWorkgroup_x86 /s /v/qn
    1. Type it as shown above. There is no space in /v/qn
  3. For the Uninstall program, look at the screenshot below. You can leave it blank for now, but go back and the proper information once the wizard is complete.
  4. In the Detection Method section, you’re going to look for the MSI file PervasivePSQLv10WGE_x86.msi; this file is also located in the same folder as the setup file in step 1.
These steps worked in my environment.


Leave a comment

Add a link to Favorites side bar (Windows 7/2008)

The Favorites side bar in Explorer is found (in Windows 7/2008) under C:\Users\%username%\Links folder. By default, this folder contains three link (.lnk) files: Desktop.lnk, Downloads.lnk and RecentPlaces.lnk.

I wrote a VB script that you can append to your network login script to create new entries in this section.




Option Explicit

‘ Create link for J drive
‘ Passing the following information to CreateLinkFile Subroutine:
‘ First: Dfs link or URL destination path
‘ Second: Link description
‘ Third: Name of link (.lnk) file
CreateLinkFile “\\Dfs\link\OrSharePath\”, “A Description”, “NameOfLnkFile.lnk”

‘ =============================
‘ Create link files for J drive
‘ =============================
Sub CreateLinkFile ( LinkTargetPath, LinkDescription, LinkFileName )

‘ Variable declarations
Dim wshShell, oShellLink, fso, strLinkFilenameAndPath

‘ Set workspace environments
Set fso = CreateObject( “Scripting.FileSystemObject” )
Set wshShell = CreateObject( “WScript.Shell” )

‘ strLinkFilenameAndPath variable holds full path where .lnk file will be saved
‘ Path is based on environment variable %USERNAME%
strLinkFilenameAndPath = “C:\Users\” & wshShell.ExpandEnvironmentStrings ( “%USERNAME%” ) & “\Links\” & LinkFileName

‘ Llink will be created only if it doesn’t already exist
If Not fso.FileExists ( strLinkFilenameAndPath ) Then

‘ .LNK file to be created in C:\Users\%USERNAME%\Links folder
Set oShellLink = wshShell.CreateShortcut( strLinkFilenameAndPath )
oShellLink.TargetPath = LinkTargetPath ‘ Absolute path to the executable, file, folder, or URL
oShellLink.Description = LinkDescription ‘ Short description, optional
oShellLink.WindowStyle = “1”             ‘ 1 = Default, 3 = Maximized, 7 = Minimized
oShellLink.Save
End If

End Sub





Leave a comment

Create New Local Administrator From Command Line

The following command line tools will allow you to:

  1. Create a new local user account
  2. Set the account from step 1 to password never expire
  3. Add the account from step 1 to the local “Administrators” group

net user /add

wmic useraccount where “Name=’‘” set PasswordExpires=false
net localgroup Administrators %computername%\ /add
I used these commands during a Task Sequence in SCCM 2012.

1 Comment

Outlook 2010 Keeps Prompting for Credentials

Issue: Outlook 2010 keeps prompting for credentials.
Environment: Windows 7 64-bit and Outlook 2010 (MS-Office 2010 SP1 with all updates)


Possible Fix 1
These steps came from the following link. These did not work for me personally, but it has worked for some people.

  1. Open Outlook
  2. Click on File
  3. Click on Info
  4. Click Account Settings
  5. Click on Account Settings option, again..
  6. Double click the Exchange Account (your name)
  7. Click More Settings
  8. Click Security Tab
  9. Check the Always Prompt for Logon Credentials
  10. Close Outlook
  11. Open Outlook
  12. Enter username and password
  13. Click on Remember my Credentials
  14. Close Outlook (repeat steps 11 – 14 at least 3 times, and don’t forget to click on Remember my Credentials)
  15. Go back into More Settings (from step 7)
  16. Security Tab
  17. Now REMOVE the check from the Always Prompt for Logon Credentials
  18. Close Outlook

Possible Fix 2
This fix came from this link. These steps did work for me and my users.

Leave a comment