Advertisements

Microsoft

  • August 7, 2012

    Enable Remote Desktop on UAG Server

    1. Open the TMG MMC 2. right click on the <Firewall Policy> in the left nav. 3. In the drop down click “All tasks” 4. Then click “System Policy” 5. Click “Edit system policy” 6. In the system policy Click “Remote Management”, “Terminal Server” 7. On the “General” tab check the check box to enable that group. Click OK, Apply, and OK again. 8. You will need to add your client machine to the Remote Management Computers or Enterprise Remote Management Computers group. 9. You should take out the access policy you added. 10. Now hit the Apply settings so UAG can add the settings http://www.microsoft.com/en-us/server-cloud/forefront/unified-access-gateway.aspx
  • I have been doing a System Center Configuration Manager 2012 (SCCM 2012) install and these guides have been a big help and so far the system is work great.  I posted the link at the bottom there are a lot of different configuration setups depending on your environment.  I know this setup works cause I did these step by step and it worked great. Using Configuration Manager 2012 RC in a lab – Part 1. Installation. Part 1, Installation [October 27th 2011] Using Configuration Manager 2012 RC in a lab – Part 2, Adding SUP and WDS. Part 2. Adding Sup and WDS [October 28th 2011] Using Configuration Manager 2012 RC in a lab – Part 3, Configuring Discovery and Boundaries. Part 3. Configuring Discovery and Boundaries [October 29th 2011] Using Configuration Manager 2012 RC in a lab – Part 4, Configuring Client Settings and adding roles. Part 4. Configuring Client Settings and adding roles [October 29th 2011] Using Configuration Manager 2012 RC in a lab – Part 5, Enable the Endpoint Protection Role and configure Endpoint Protection settings. Part 5. Enable the Endpoint Protection Role and configure Endpoint Protection settings[November 5th 2011] Using Configuration Manager 2012 RC in a lab – Part 6, Deploying Software Updates. Part 6. Deploying Software Updates [November 5th 2011] using Configuration Manager 2012 RC in a LAB – Part 7. Build and Capture Windows 7 X64 Part 7. Build and Capture Windows 7 X64[November 6th 2011] How can I import computers into Configuration Manager 2012 using a file ? Importing Computers using a file in Configuration Manager 2012 [November 11th, 2011] using Configuration Manager 2012 RC in a LAB – Part 8.Deploying Windows 7 X64 Part 8.Deploying Windows 7 X64 [November 12th, 2011] using Configuration Manager 2012 RC in a LAB – Part 9. Adding an Application, editing a Deployment Type, Copying...
  • After moving the System Center 2012 Configuration Manager (SCCM2012) SQL Site Database to another drive, creating a new Software Update package or a new application fail Symptoms After moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update group, Software Update package, or creating a new application fails and errors similar to the following are logged in the SMSProv.log file: *** *** Unknown SQL Error! SMS Provider 14-03-2012 07:56:47 2016 (0x07E0) *~*~*** Unknown SQL Error! ThreadID : 2016 , DbError: 50000 , Sev: 16~*~* SMS Provider 14-03-2012 07:56:47 2016 (0x07E0) *** [24000][0][Microsoft][SQL Server Native Client 10.0]Invalid cursor state SMS Provider 14-03-2012 07:56:48 2016 (0x07E0) *~*~[24000][0][Microsoft][SQL Server Native Client 10.0]Invalid cursor state *** Unknown SQL Error! ThreadID : 2016 , DbError: 0 , Sev: 0~*~* SMS Provider 14-03-2012 07:56:48 2016 (0x07E0)   SQL Profiler provides the following additional details: An error occurred in the Microsoft .NET Framework while trying to load assembly id 65539. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: System.IO.FileLoadException: Could not load file or assembly ‘cryptoutility, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A) System.IO.FileLoadException:    at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)    at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)    at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)    at System.Reflection.Assembly.Load(String assemblyString) Cause This can occur if the SQL Site Database MDF and LDF files are moved to a different drive. For example, if originally the Configuration Manager Site Database was created on C:Program filesMSSQL serverdata but then later the MDF and...
  • I was having and issue with a windows server print drivers and print processes at a client and this information and article helped me out tremendoulsy. There are three basic modes of isolation that can be configured for individual print drivers: None – in this mode, print driver components are loaded into the spooler process. This is essentially the model found in previous versions of Windows Shared – multiple drivers that are set for isolation are loaded into a single shared process space that is separate from the spooler process. Although this protects the spooler process, the drivers that are in shared mode can affect one another Isolated – each driver is loaded into its own process space. This protects the spooler from individual driver failures, and also protects drivers from each other Remember that the modes are configured on a per-driver and not a per-system basis. One other point to keep in mind – not all drivers will run in shared or isolated mode. Drivers that call spooler functions or a printer’s configuration module directly will need to run in “none” mode. The driver developer can advertise whether or not their driver supports isolation mode. Now lets take a look at how the new model works. Anytime shared or isolated mode is used for a print driver, a new process – PrintIsolationHost.exe – is launched by the DCOM Server Process Launcher for each “print sandbox”. The print processor, the rendering module, the configuration module and the miscellaneous driver files are loaded into the address space for the new process, instead of the spooler’s process. The spooler essentially proxies calls for the print processor and other driver components in the PrintIsolationHost.exe process and DCOM is used for inter-process communications. Something to note here – if you examine the spooler closely you’ll find that...
  • July 1, 2012

    Office 2010 KMS Activation Issue

    Went to stand up Office 2010 KMS server on an existing 2008 server.  I went to install Office 2010 key management host and I get “Unsupported Operating System”.  So I decided to install on 2003 license server again already existing and I get the same error.  I run the key management host on my windows 7 computer thinking maybe I received a bad download runs with no issues.  So after some digging threw office 2010 beta and official release documentation and a few Google searches I found out some very interesting information.  Office 2010 KMS only runs on Windows 2003, Windows 2008 R2 and Windows 7 all other operating systems are not supported.  Microsoft has released a patch to help those still running 2003 KMS server.  But so far no patch for the 2008 server the only fix I have found for that is to upgrade to R2. http://support.microsoft.com/kb/968915/en-us
  • Log into SCCM and click on query and create this query to find broken SMS clients ( System Resource.Client is equal to 0 or System Resource.Client is Null or System Resource.Agent site is not equal to “D80” ) and System Resource.Operating System Name and Version is like “microsoft%” and System Resources.SMS Assigned Sites is not Null
  • June 10, 2012

    Installing New SCCM CA on IIS 7

    1.Open the IIS manager console 2. Click on the server name 3. Click Server Certificates 4. Right Click and select Create Domain Certificate 5. Complete all the needed information and select your certificate store server. Make sure you use the FQDN for the server in the Common Name section. 6. Right Click on Default Web Site 7. Click edit Bindings 8. click on edit for https then select your newly issued certificate 9. You do not need to reboot the server or restart IIS.
  • Fix: Could not start the Automatic Updates service on Local Computer. Error 0×80004015: The class is configured to run as a security id different from the caller Issue: Automatic Updates (AU) service will not start attempting to start the service manually results in the following error on a Windows XP SP3 machine: Could not start the Automatic Updates service on Local Computer.  Error 0×80004015: The class is configured to run as a security id different from the caller Solution From a command prompt re-register the Automatic Updates dll by running: regsvr32 /u wuaueng.dll regsvr32 wuaueng.dll Change the Automatic Updates service startup from to Automatic if this is not done already.  The Automatic Updates service should now start on its own on reboot.  Make sure Background Intelligent Transfer Service (BITS) and Windows Management Instrumentation (WMI) are both set to Automatic as well before reboot.  Sometimes if this happens as a result of a virus you will need to adjust those settings.
  • Click Start, Run and type control schedtasks Double-click Add Scheduled Task. The Scheduled Task Wizard starts. Click Next. Under Click the program you want Windows to run, click Browse. In the Select Program to Schedule dialog box, locate the %SystemRoot%System32 folder, locate and click the Shutdown.exe file, and then click Open. Under Perform this task, specify a name for the task and how frequently you want this task to run, and then click Next. Under Select the time and day you want this task to start, specify a start time and date for the task, and then click Next. Type the user name and password to run this task under, and then click Next. Click to select the Open advanced properties for this task when I click Finish check box, and then click Finish. Click the Task tab. In the Run box, specify any additional parameters that you want to use with Shutdown.exe. Click OK. Important: In the 10th step, you need to add the parameters for the Shutdown.exe command. To immediately shutdown the system (0 second timeout), the command-line would be: shutdown.exe -s -t 00 To reboot the system immediately, this command: shutdown.exe -r -t 00 For additional help, type Shutdown /? at the Command Prompt. Scheduling the Shutdown.exe without any parameters will not help. It will just execute with a exit code 0 (success)