binarymime

You could try LANegram: http://www.softpedia.com/get/Internet/Chat/LAN-Messaging-Clients/LANegram.shtml

I have recieived an email from my support agent explaining that he has brought the issue to the product grp and that he would get back to me with a possible solution for this type of situation. I will post back as soon as i hear something further

I am experiencing the exact same issue, and have a post on the technet forums regarding this: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/8faa337b-a648-49b4-8431-49c022b96e04 Based on my testing and research this occurs with any processors that do not support the NX bit. As of the Win 8 RTM release Microsoft has been enforcing a setting by which Win8 can only be installed on processors that support this functionality. As a genral rule of thumb pentium 4 processors that support Hyper-Threading and above or processors that support 64-bit operating systems (ie. Core Duo, Core 2 Duo, etc) seem unaffected. Because WinPE 4.0 is based on Win8 Bootloader this seems to be causing the problem, even though you only plan to install windows 7. Regardless i have a call in with Microsoft support as in my opinion this is completed unnacceptable, i will post back any further leads. Thanks

The msg command replaces netsend in Vista and above, usage can be found in the link below or by running msg /? from the command line. http://pcsupport.about.com/od/commandlinereference/p/msg-command.htm If you are nostalgic as all hell then you can use third party apps to utilise net send, however this normally requires a scripted delivery of a client to each workstation. Thanks

0x8004005: SYMPTOMS: - When attempting to image a computer you recieve the message: "an error occurred while retrieving policy for this computer (0x8004005)" CAUSES: - This error can be caused by clock syncornization issues between the client, DC, and FS. RESOLUTION: - Ensure the BIOS clock is syncronized with your Domain Controller and try again.

0x80070057: SYMPTOMS: - When attempting to image a computer you recieve the message: "an error occurred while retrieving policy for this computer (0x80070057)" - Additionally upon examining the SMSTSlog file in X:\windows\temp you may find the following errors: MP Location returned and empty site code CCM::SMSMessaging::GetMPLocation failed; 0x80004005 Failed to query http://fqdn for MP location CAUSES: - This error generally accompanies the use of SCCM Bootable Media, such as a CD or DVD and is most commonly associated with Apple Computers - This is most commonly caused by issues with the self-signed certificate used by the bootable media RESOLUTION: 1. Contact your SCCM administrator to obtain a new bootable media CD with a fixed PXE certificate

Complete shot in the dark here...i have had flakey issues in the past if STP (Spanning Tree Protocol) was enabled on my switch...something to check and like i say shot in the dark. By design STP should not be interferring with this at all...but like i said in our case it was, i didnt find a relevent reason to investigate the issue further as it turned out we upgrade many of our situations at the onset of the problem.

So are you using WSUS? or Software Update Services from your configuration manager console? If you are using the SCCM iteration of this then you should be able to supress device restarts under the deployment properties of the software update. Under the user experience tab change the following: 1. User Notifications: Hide in Software Center & All Notifications 2. Device restart behaviour, check of both boxes to suppress the system restart on the following devices Hoep that helps

You will have to configure the instance to use a static port, this can be done from "SQL Server Configuration Manager" 1. Open your instance 2. Open the properties for "Named Pipes" and change enabled to "Yes" 3. Open the properties for "TCP/IP" and click on "IP Addresses" 4. For every IP interface change the "TCP Port" field to your chosen static port 5. For the "IPAll" Interface change the value of the "TCP Port" field to your chosen Static Port 6. Ensure the "TCP Dynamic Ports" field is blank. 7. Restart your SQL services for the named instance Document the Port number and allow it through your firewalls where applicable. You should now be able to install the primary server to it Let me know if you have further questions

I imagine the following maintenance tasks would do this for you, (assuming you are running SCCM 2012): Delete Aged Inventory History Summarize Installed Software Data

Have you tried just running it from the distribution point? I ussually had hanging issues like that if files were sometimes corrupt. You could try copying the file from the source media and redistributing your source files to see if that changes anything. Thanks

At our Core backend "Data Center" we have a Primary Site Server VM and an SQL Server VM: TEST-SCCM-A (Hosts Primary Site Server, Source files and folders, and acts as the distribution point for our Data Center) - Contains a System partitition - Contains SCCM Data Partition TEST-SQL-A (Hosts the SQL Database for SCCM) - Contains a System Partition - Contains SQL Data Partition At our Secondary Sites / Schools: We run one Dell server at each site running VMware, each server hosts two VM's, a Domain Controller (DC), and a File Server (FS). We leverage the file server for the SCCM Distribution point: TEST-DC (Local DC) - Contains a System Partition TEST-FS (Acts as the file server for the school, PXE Services, Distribution Point) - Contains a System Partition - Contains a DATA partition for Staff / Student access - Contains SCCM Data Partition On each server we use the NO_SMS_ON_DRIVE file to control where the package repository stores its data, we place this file on any partitions present on any of the servers (including removable drives, if present) that will NOT be hosting SCCM Data. This ensures our package repository is always on the same drive. Does that answer your questions?

Have you tried running from the ditribution point and copying local and then running, both should be flags on the package / program, i had an instance where this was happening to me during osd specifically and the fix was to have the software installation taks copy the files local first and then execute.

I have done some more digging and it seems that each time i try and generate an elert, this is logged under componenet status for SMS_ENDPOINT_PRTECTION_MANAGER: Endpoint Protection Manager failed to generate malware detection alerts for type:"31". Verify that the site database is configured correctly. Error code returned is:"0x87d20002". I removed and re-added the forefront protection role on my primary site server and this problem still has not been resolved Any ideas...i am desperate

When is this occuring? Through OSD or from within windows? Are you using SCCM 2007 or SCCM 2012? Thanks

Primary server and SQL server along with DP's are all hosted on vmware virtual machines, i have never had issues with the 2008 installation, just followed the wizard. I would recommned that you install it with the default instance intact and then add a dedicated SCCM instance on top of it, there have been indexing issues in past release when not keeping the default instance intact. I should correct myself that we are using SQL 2008 R2 SP2 with no CU. Also as an added tip, when you create your boundary groups, use one group for site assignment, and create a seperate boundary grp for distribution points Thanks

For our school division we have approximately 3000 clients spread out over 42 sites, config is as follows: 1 Primary Site 1 SQL Server (Remote) 42 DP's As stated above, do not use a CAS, totally unnecessary, you would only need one if you had more than one Primary site, and you would only need more than one primary site if you were reaching the theoretical limit on the amount of clients supported in one primary site which is 100,000. This works perfectly for our situation, however in our case we use 80GB dedicated partitions for DP's, i cannot stress the importance of having adequate disk space for ditribution points and future growth, i also strongly advise a dedicated sql server, hosting them both on the same box will drag your performance down depending on how heavily the SQL database is taxed Regarding the version of the SQL server, always check the SCCM whitepaper, i believe the newest currently supported, which we are using is 2008 R2 CU 6..., when 2012 is supported, just do an in place upgrade (i am totally assuming you can) if not just migrate your database to a replacement 2012 server when the time comes...maybe im just not sure why you specifically want a 2012 SQL server over 2008...in my opinion always go with the newest supported

Hi Tay, I actually spoke to a SCCM 2012 guy at a microsoft tech day event, he looked into this for me and essentially the reasoning is this: Your client machine will show local time, as will your server with forefront installed or role added, however the actual reporting is done in UTC time, thus the 5-6 hour offset depending on your timezone. Unfortunately this is present in both 2007 and 2012 and it is by design and cannot be changed. You will simply have to +/- the time difference. I know its annoying, but i had the same issue, i wish it reported based on the local time of the hosting server or client that reported back....but it doesnt

I am having some wierd issues with Forefront e-mail Alerts, they worked perfectly in 2007 once i got by the configuration hurdles, however in 2012 i cannot for the life of me figure out why they are not working: I have deployed a client policy for forefront and confirmed that the policy is applying I have deployed a default antimalware policy and it is applying as well. I have confirmed that my smtp settings are working and that i can send a test e-mail I have configured antimalware detection and outbreak alerts on the collection of which my test box is a member. I have configured a subscription to the said alerts and assigned my email as the recipient When i download the eicar test file from http://eicar.org/86-...tended-use.html it is immediately detected by forefront, within about 20-40 seconds it is removed and reported as such under the malware detection alert. However no e-mail alert is being triggered and sent to my account...i cannot for the life of me figure out why as in my opinion the alert trigger criteria is being met... Any ideas as to why this would not be working? Thanks

Hi jmac, My apologies i should have quoted the post i was responding to, my solution was intended for saulw's inquiry. However to answer your question; all you should have to do is change the backup location. The only other thing i would make sure of is that you have a domain administrator account with permissions to the site database and the folder on the remote location to which you will be backing up. Thanks

I would be happy to assist 1. First things first. Make sure you have a backup of your site server and SQL site database. 2. On your site server browse to your ConfigMgrSP2 Install files. Depends where you have them stored...in my case we have all of our instllation media stored on a file server in ISO format so we mount them with Virtual drive software. 3. Run "splash.hta", when it loads click "Configuration Manager 2007 SP2" 4. Select "Perform site maintenance or reset this Site" and click "Next", ensure all data in the following screens is correct and follow the onscreen instructions. Let me know if you have questions {Edit} I forgot to mention that following this procedure i had to uninstall my head end management point role, and pxe role, and then re-add / re-install them to get my PXE Service point to work again...in case you are getting a "Failed to download policy" message on any client you try to roll out. This entry will appear in the SMSTS.log file Thanks

I have modified a version of the following computer rename script. Details of the edit can be found in the header of the script, however this script will not allow blank input and does a check to ensure that the computername is 15 characters or less, if neither conditions apply the task sequence aborts. Also you need to set your task sequence up so that it does a conditional check on the value of ALLOWOSBUILD. If the value = "No" then the task sequence will abort: '========================================================================== ' NAME: ZTI-ComputerName.vbs ' ' AUTHOR: Nick Moseley ' DATE : 6/1/2009 ' ' v1.2 Edit: Christopher Nienaber ' DATE : 4/4/2012 ' ' COMMENT: This script will detect if the current assigned value for the computer name ' begins with MININT, indicating that this image is bare metal image. It then prompts ' the end-user to enter a new computer name. ' ' VERSION : 1.1 ' 1.0 (12/08/2008)- Intial script to check if the computer name begins with ' "minint", which indicates the system was booted with CD or PXE. ' 1.1 (06/01/2009)- Added check if the computer name equals "minwinpc", ' which indicates the system was booted with USB key ' 1.2 (4/4/2012)- Added check to ensure name is less than 16 characters, and that name ' is not blank '========================================================================== Dim sNewComputerName, oTaskSequence, sTSMachineName, bPromptName, oAllowBuild Dim bLength Dim mBox Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") Set oAllowBuild = CreateObject ("Microsoft.SMS.TSEnvironment") ' Get the name the computer is set to receive and truncate to first 6 letters sTSMachineName = lcase(oTaskSequence("_SMSTSMachineName")) If left(sTSMachineName,6) = "minint" Then bPromptName = True ElseIf sTSMachineName = "minwinpc" Then bPromptName = True Else bPromptName = False End If ' Note: The wscript.echo commands are logged in SMSTS.log for troubleshooting. They are not displayed to the end user. If bPromptName = True Then wscript.echo "Detected that the computer name is scheduled to receive a random value. Prompting user to input a standard name." Do sNewComputerName = InputBox ("Enter Desired computer name to continue.", "ComputerName", , 30, 30) If sNewComputerName = "" Then bLength = False End If ' Check Length - Must not equal null and must be less than 16 characters If Len(sNewComputerName) <= 15 and Len(sNewComputerName) >= 1 Then bLength = True Else wscript.echo "Computer name must not equal null and must be less than 16 characters, prompting user to re-enter name." mBox = MsgBox ("ComputerName must not equal null and must be less than 16 characters, click ok to enter a new name or cancel to abort the task sequence!",1,"Invaild Computer Name") End IF If mBox = 2 Then Exit Do End If Loop While Not (bLength) If blength = True Then oTaskSequence("OSDComputerName") = UCase(sNewComputerName) wscript.echo "Set Task Sequence variable OSDComputerName to: " & sNewComputerName oAllowBuild("ALLOWOSBUILD") = "YES" wscript.echo "A proper computer name was entered, continuing task sequence!" Else oAllowBuild("ALLOWOSBUILD") = "NO" wscript.echo "Task Sequence aborted by user!" End If Else wscript.echo "Computer Account already exists in SCCM Database, continuing Task Sequence" oAllowBuild("ALLOWOSBUILD") = "YES" End If

One of the most time consuming tasks in an IT administrators job is the maintenance of Software updates, in particular the configuration and maintenance of third party software update packages. The purpose of this post is to provide an in depth guide to achieving this using a combination of the following tools: SCCM 2007 SCUP 2011 iExpress (Windows 7 Self-Extracting .exe packager) Scripts (in this example batchfiles - .bat) Orca An intermediate knowledge of the windows registry This guide assumes that you have installed and configured the SUP role on at least one of the servers in your organization as described here CONFIGURATION: 1. Install Orca MSI Editor Download and install orca 2. Install .NET Framework 4.0 Download and install .NET Framework 4.0 3. Install SCUP Download and install SCUP 2011

Well i managed to figure out my problem after hours of sifting through mounds of articles on line and the sccm logs on my primary site server. Turns out my STATUS_SUMMARIZE, SITE_COMPONENT_MANAGER, and SCCM_SITE_BACKUP componenets were corrupt and not installed properly...not sure how this happened, regardless i did the following, i ran a repair install from my configmgrsp2 sourcefiles and voaila, every component installed correctly. This has also fixed an issue i was having with my sms_executive not creating a crashdump every time it stopped.

No i have verified that i was running the correct one. Thanks