Which Objects to be used for .net API out of SPSite(server) or Site(client)
hi,
I am newbie to sharepoint.I am creating a share point 2010 publishng site.I am also going to create few custom visual webpart using .Net API using C# to populate my Sharepoint list data to users.I have found Server and Client objects in sharepoint Like "SPSite","SpWeb" etc... server object equivalent Client object as "Microsoft.Sharepoint.Client.Site" so in my coding using which object is prefarable.Can any one explain with sample scenarions means will be great.
Thanks & Regards, Krishna
- Edited by Krishna_2011 Friday, February 3, 2012 2:39 PM
Reply:
Corey Roth - SharePoint Server MVP blog: www.dotnetmafia.com twitter: @coreyroth
------------------------------------
Reply:
Thanks Corey For Reply,
I got it.But one clarification if i am going to create one Publishing Intranet/Internet Portal in sharepoint 2010 where our client organization needeed it.So in such case our client may be going to access it either Intranet or Internet.So before developing code for this site which Object model i can go.Can you elaborate more on this.
Thanks & Regards, Krishna
------------------------------------
Reply:
Corey Roth - SharePoint Server MVP blog: www.dotnetmafia.com twitter: @coreyroth
------------------------------------
Reply:
1.Can you provide me few examples for the items which sits on Sharepoint server Itself and not available if it is out of sharepoint server.
2.In the performance point of view which can be preferable to use either Client or Server object model to the code which sits on Sharepoint server itself.
Thanks & Regards, Krishna
------------------------------------
Reply:
Corey Roth - SharePoint Server MVP blog: www.dotnetmafia.com twitter: @coreyroth
------------------------------------
Patch updation
Hi,
in my zone push software updates in all location bdps all are reached but one location systems directly connected to sccm mail server network over uetilizied when i adevertised downloaded and install option selected which log ineed to check why thease location systems not connected bdp directly download updates from mail server kindly help.
Kiran
Reply:
I think you are asking why in one of your locations why clients are not connecting to their local BDP, and instead are connecting to your mail server, which I'm guessing is set up as a distribution point
Is this correct?
Cheers.
------------------------------------
Reply:
yer clients are not connecting to local BDP all clients updates taken for site server.
Kiran
------------------------------------
Reply:
You need to look at your boundaries.
First look here: http://technet.microsoft.com/en-us/library/bb680558.aspx
Secondly, you will need to look at configuring your BDP's are protected BDP's. This will force clients within the same "boundary" as the BDP to use that particular BDP.
Look here for more information on protecting your DP's. http://technet.microsoft.com/en-us/library/bb932133.aspx
Cheers.
------------------------------------
Forums 4 - Release 35 - February 6
Release Details
This forums release had two main goals
- Update to the rich text editor
- Updates to address performance issues in the application, especially for thread page load times for thread that had more than 40 replies
We also expect the performance issues to improve overall stability and availability of the application. In addition to the above there have also been numerous bug fixes.
Known Issues
Editor: Edit code in Google Chrome drops line breaks. When users edit code after it has been submitted, the edit code dialog drops the line breaks. To get around this copy the code and re insert it (instead of editing the code in place).
Community Forums Program Manager
- Changed type Brent Serbus Tuesday, February 7, 2012 12:35 AM release notes
Hyper-V VPS Disk I/O bottleneck??
I am facing a weird disk I/O issue on my Hyper-V node. I have 4 x 1TB disks in RAID-10. We have around 10 Virtual Machines running and still there is some issue with the disk I/O.
When we perform a disk intensive activity on the node, then the Disk I/O can easily go upto 150Mbps. But when any disk intensive activity is performed on a VPS, the disk I/O cannot go over 10Mbps even when there isn't any load on the node.
Would really appreciate a little help in this regard. Is there some setting which has to be changed so that VPS can overcome the disk I/O bottleneck of 10mbps?
Thanks in advance!
- Changed type Vincent Hu Friday, February 10, 2012 8:00 AM
Reply:
Philip Elder SBS MVP Blog: http://blog.mpecsinc.ca
------------------------------------
Reply:
Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Backup, test your backup, try new things. Attempting change is of your own free will.
------------------------------------
backing up hyper-v server running sbs 2011 to the cloud
Scenario: 1x windows server 2008 r2 in hyper-v running SBS 2011 VM. I set up a backup to a 1TB Lun from the SBS 2011 console through iSCSI to a QNAP NAS (TS-459 Pro II Turbo). It has been going great so far but I would like to now set up a backup to the cloud for extra redundancy.
Questions for a discussion:
1. You cannot backup the LUN itself to the cloud as it is locked by the SBS backup. Fortunately, QNAP devices provide a safe way to backup a LUN. I have set it up that it backs it up to another folder inside the QNAP. I now have a 1TB file backup of the LUN that I can use to backup to the cloud. My options are many as QNAP provides native connectivity to a few providers(S3, Elephant Drive, Symform) or any other that supports rsync.
I am stuck now having to transfer the whole 1TB LUN over to the cloud. I am testing to see if it only would transfer the deltas (created rsync server within QNAP and backing it up to itself for the first time, taking 55 hours).
If only deltas, with the Amazon S3, I would only have to pay 14 cents / GB, so that is around $140 for the first TB and then deltas would be at around 5GB a week / backup. Pretty good but not sure if that is how it would work.
The actual backup data itself is at around 300GB. I would imagine one can script wbadmin tool to perform a backup on weekends seperate from SBS backup to a folder on the QNAP and rsync this folder over to the cloud.
Curious how others address this...
2. My other question relates to backing up the HOST OS Hyper-V Server. Is it enough to back just the hyper-v server alone, or just individual VMs, or both? I have SBS 2011 backing up twice a day, should I start backing up the physical OS once a week at the end of the week?
For restoring purposes, believe either one will do, which would have the fastest restore time in case of a system failure and best practice? I cases such as the VM itself is corrupted, or physical server hardware problem, or a fire destroys everything.
Reply:
Why bother backing up the HyperV at all? (OK, this idea may take some getting used to)
The HyperV server should not be domain joined and should be a most simple installation. Anything goes wrong with it, FORMAT C: and install anew is going to be as quick as any restore, and quite likely as quick as repair attempts. Consider the HyperV installation 'disposable'.
OK, when I build my HyperV's I already have this 'in mind', so there's nothing but the OS on C:, all VHDs are on a separate partition (actually, a separate RAID array). Backup is then used inside the VM, with restore also happening inside the VM, should it be necessary. One could additionally do backup of the VMs, or just the VHDs, from the host, if one required an alternate backup/restore.
I don't do cloud backup, but if I did I'd be looking at direct from VM to cloud.
------------------------------------
Reply:
SuperGumby,
Thanks for the reply.
If you remember, I used your suggestion and created on large partition for all the VM vhds over a raid 6 partition. Has been working well so far.
Unless you are doing HA and failover clustering, you are correct to say that hyper-v is disposable. This is why I do not currently back it up. I just wanted to hear other opinions on this.
I am surprised, as it seems not many people here backup to the cloud. With so much buzz about it, thought more it pros would be testing it in their environments.
------------------------------------
Server 2003, full LAN/WAN access, no access to www (internet)...totally stumped
Windows Server 2003 R2
Active as DC and DNC, DHCP controllers.
Everything has been set up properly and working smoothly for many years now (since 2007) -- so not a configuration issue as far as I can tell.
Suddenly lost www (internet) connectivity on 2011-11-21 -- unable to ping any major websites. Discovered this because virus definitions stopped updating.
All WAN/LAN features and connectivity working properly. I can remote in normally.
Does have Symantec Endpoint Protection Manager and Client installed. Server also acts as a virus definition distribution site to client computers.
Have double checked all IP settings pasted below.
Windows IP Configuration
Host Name . . . . . . . . . . . . : trouble01
Primary Dns Suffix . . . . . . . : NWG.XXXXXXXX.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : NWG.XXXXXXXXX.com
XXXXXXXX.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Ad
apter
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.8.3.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.8.3.1
DNS Servers . . . . . . . . . . . : 10.8.3.10
10.8.1.3
Primary WINS Server . . . . . . . : 10.8.1.3
I have yet to uninstall/reinstall driver for NIC, firmware upgrade for NIC as these require me or someone to be onsite at server located a few hundred miles away. I am pretty confident it is not a firewall/blacklist error due to our WAN setup and client computers running through the same switch and router have access to www.
Please help!! Any comments or suggestion welcome. Or even if any of you have even encountered a problem like this before, some comaraderie would be welcome lol.
Reply:
Hello,
which machine is 10.8.1.3, different subnet? But you are talking about one DC only?
4 weeks ago this started or is this a typo?
Are you able to ping your router?
Did you talk to the ISP about connectivity problems?
Please describe the complete network built so we get an overview.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
------------------------------------
Reply:
Our company has several physical locations so each location has a subnet. 10.8.1.3 is the "primary" DC on the 10.8.1 subnet that is also a DNS. All subnets are connected to a AT&T VPN, which is then connected to our parent company's network, which is then connected to an ISP, and then to the WWW.
Given that I can access the WWW from any other client or computer on our company WAN, minus the server in question, would contacting the ISP do anything?
This started 2011-11-21, not a typo, more like 8 weeks ago, there have been some personel changes recently so this should have been solved much earlier.
Yes, I can ping our router connected to the server...but again this is the stumper...all LAN/WAN functions are seemingly operational.
From my viewpoint, the problem seems to local, on the computer, not having anything to do with our network. However, my networking skills are severely limited so I welcome any opposing views.
thanks again!
edit: though I check Symantec Endpoint Protection, I'm not completely familiar with that software so it is still possible that it is a virus scan issue, as this is the only similar case I have encountered like this.
- Edited by Tiger3k Tuesday, January 24, 2012 11:18 PM
------------------------------------
Reply:
Have you upgraded or made any changes to the SEP product? What client features are installed on the server? Have you tried disabling the NTP (firewall feature) on the server?
It is possible the server has an infection. If that is the case, you can run the Power Eraser tool to rid the system of hard to detect threats.
http://www.symantec.com/security_response/malware.jsp
The next option would be to run a scan with the SERT utility.
http://www.symantec.com/business/support/index?page=content&id=TECH131732&locale=en_US
Let me know how it goes for you.
Best,
Thomas
------------------------------------
Reply:
Yes, I disabled NTP on the server. I even went so far as to disable all the SEP services, short of this I would have to uninstall SEP which I did not do. I will run the Power Eraser and SERT utility and give an update. **EDIT: do I still need to do this if I manually updated the virus definitions and ran a full scan? The Power Eraser tool webpage is dated to 2011-10-28, not sure what the tool is dated to. Reading the SERT documentation, that seems like worthy try either way.
What did fix the issue is changing the IP address of the server. However, changing it back to the original IP address "unfixed" it.
To me, this hints that there is definitely some application layer issue...but again, my network skills are severely limited!
- Edited by Tiger3k Wednesday, January 25, 2012 5:04 PM
------------------------------------
Reply:
Hi, Sorry for the delay in responding, I missed your response somehow. Yes, you should run the Power eraser/SERT tools even if you tried running a scan with the latest rapid Release defs. The date of the tool is just the last version release date.
Let me know what happens.
Regards,
Thomas
------------------------------------
IE 8 support in Windows 7
- Changed type Hypvcn Monday, February 6, 2012 4:46 PM
Reply:
Hi,
no you are incorrect. the latest news about IE from MS can be read on the IEBlog.
Regards.
Rob^_^
------------------------------------
The security database on the server does not have a computer account for this workstation trust relationship
Please help - I'm getting crazy. Four machines, after SP1, two with this login problem. I'm getting the message "The security database on the server does not have a computer account for this workstation trust relationship.". I updated the network card driver, I removed computer from domain and rejoined. Nothing helps.
First login works fine, second one gets the error message again. Please help. User and I don't know what to do!
Any help would be appreciated.
Best wishes
Roberto
- Moved by Carey FrischMVP, Moderator Tuesday, May 10, 2011 11:20 PM Moved to more appropriate forum category (From:Windows Vista Service Packs/Windows Server 2008 Service Packs)
- Changed type Carey FrischMVP, Moderator Friday, February 10, 2012 3:21 AM Discussion
Reply:
Having same issue. The same system is OK on a simple domain (no special GPOs) but our work domain has this issue. The work domain has some "special" things.
Do you by chance have a GPO which changes the primary domain suffix?
------------------------------------
Reply:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2875206&SiteID=17
I have a GPO that does set the primary domain suffix.. ill try and kill the setting and see if it changes anything.
------------------------------------
Reply:
------------------------------------
Reply:
------------------------------------
Reply:
sorry for an uninformed question but how do you kill the setting exactly? I cant find that GPO?
thanks
peter
------------------------------------
Reply:
ok, so i found in computer configuration/administrative templates/network/dns client/primary DNS suffix ... but it is not configured. am i looking in the wrong place?
------------------------------------
Reply:
on a PC that's having trouble, go
start -> run
rsop.msc
it will probably bring up a UAC thing, just login with any admin user.
then go the the above place (computer configuration/administrative templates/network/dns client/), and see if the Primary DNS suffix is set. If it is, then you have another policy somewhere that's setting it.. if its not set... then you might be stuck
------------------------------------
Reply:
removed the computer from the Active Directory on the SBS2003, then rebooted the workstation (actually also rebooted the server) and was able to login again. ugh ... thanks guys ... this at least put me in the right direction. as an fyi, my bluetooth (logitech) and radiocontrolled (SONY) keyboards and mice on multiple machines stopped working last week with some odd incompatibility/Win95 error. i was hoping that SP1 fixes it, which it did!
------------------------------------
Reply:
Hi
I'm getting the exact same problem on a Vista Business PC/SBS2003 setup. Before I updated to VistaSP1, I'd get this, but after 4 or 5 goes it would eventually connect. However, I've just finished upgrading to SP1 and nothing will work. I've tried removing PC from Active Directory and the resetting it, I've tried just removing it from AD, I've checked RSOP (no settings there at all), still nothing works!! Does anyone have any other ideas I can try.
Cheers
MannyW
------------------------------------
Reply:
Manny,
try to remove the workstation from the domain and make it a 'workgroup' box. then restart and rejoin to the domain. then restart and see if it works (I am not saying that this is pretty but the only way to make it work for me on one of the machines).
peter
------------------------------------
Reply:
Try this out on your Domain Controller:
A) Start > Run > ADSIEDIT.MSC
B) Go to Domain Partition and mark the affected computer
C) Rightclick and Properties.
D) Doubleclick ServicePrincipalName
E) Add new value: HOST/yourcomputername.yourdomain.xyz or whatever HOST is missing.
Best wishes
Roberto
------------------------------------
Reply:
Peter
Thanks for this, I did get round to doing exactly that and, yes it does work and yes, it's seriously not pretty!!
Although this issue has gone and login is now ok, I've ended up with a new user, in the format username.domainname.local.001. As all my settings are with the prior user, big problem!! So I'm going to uninstall SP1 and System Restore back to yesterday and hope I get my original user back!
I'm really not sure why Vista invents a new user and doesn't give you the option to connect to the prior one and I'm still no nearer to figuring out what is behind this login issue; is there a setting on the Vista PC that holds the PC/Server relationship settings?
Anyone any further ideas?
MannyW
PS I'm also going to try Roberto's idea and see if that helps
------------------------------------
Reply:
Roberto,
This worked perfectly. it appears that the Domain Suffix GPO was doing it's job, but the SPN wasn't being updated properly.
Obviously, this is a workaround, not a fix, but it'll do in the meantime. We won't be able to roll out SP1 in our environment until this bug is fixed. Bummer.
Thanks again!
-Bozford
------------------------------------
Reply:
Just curious as to if anyone else out there is still seeing this issue. We still are at Princeton. If we either send SP1 via WSUS or even have someone manually apply it about 1 out of every 5 installs gets the "The security database on the server does not have a computer account for this workstation trust relationship" after SP1 install. We do have a premier ticket in with Microsoft, but no answers yet.
Princeton IT
------------------------------------
Reply:
Peter, this works fine in my case but after two reboots the problem comes back. I'll try the ASDI solution below also.
Vista Business, the problem appeared right after applying SP1.
Thanks,
Antonio.
------------------------------------
Reply:
ALL the solutions on this forum and others have no permanent solution. There is an update from Microsoft that still doesn't fix the problem.
In my case, all work-arounds failed. Apparently I just have to wait till MS gives this better attention -though I doubt they will now with 2008 and all.
------------------------------------
Reply:
probably there is a user domainName\MachineName in your local administrators, remove it from the administrators group,
this is works for me,
------------------------------------
Reply:
Im having the same error problem while connecting a terminal session to a domain. Its not an issue that can be changed by adding/removing this 'computer' from the domain. Is there an account policy setting im missing in Server 2008? Or how do i find a computer account for a Terminal session? Is this an authentification issue because there is none setup on the server as yet. It will not be possible to add the user as an administrator, the user is a member of Remote Desktop Users and Domain Users group. Have i missed something?
------------------------------------
Reply:
Hi I'm still stuck with this problem!! What was the MS update, do you have the KB number for this (or any other ID)?
I'll give anything a try !!
Cheers
MannyW
------------------------------------
Reply:
solution:
Computer to computer properties
Select the Tab which allows you to change the computer Name.
Ensure the computer name domain and suffix are in sync with the Domain (name).
Good Example>
Full Computer Name: DougLubeyComputerName.mydomain.com
Domain: mydomain.com
BAD example> (WHICH WILL CAUSE THE ERROR after upgrading to Windows vista SP1)
Full Computer Name: DougLubeyComputerName.mydomain
Domain: mydomain.com
Bad example is missing the ".com" after the "mydomain".
to note: the old style/old procedure on our network was to use the bad example becuase our computers would
not properly join the domain if we used the fully qualified domain name "mydomain.com". We had to use just
"mydomain" for the computer name, while full qualified domain name was automatically picked up whether or not
we entered "mydomain.com" or just "mydomain".
Anyhow...it was pretty simple fix.....my just adding ".com" in the computer name. Did not have to rejoin the domain or delete computer account names or edit the registry or anything......some a 30 second fix.
SPECIFIC ERROR WAS: The security database on the server does not have a computer account for this workstation trust relationship.
Thanks,
Doug Lubey of Louisiana
------------------------------------
Reply:
- My network settings are perfect. xxx.xxx.loc and DNS is perfect
- Installed Vista SP1 (reformatted my system, because of other Vista problems - Previous Vista Ultimate SP1 did not have this issue)
- I can join domain, but get the error
- I have no GPOs in use
My last Vista system ran fine with SP1, this one does not... nice! I can't take the Vista pain anymore... I hate to say this since I have been so die hard microsoft, but this is ridiculous, so buy a computer that works... aka NOT Vista
If anyone actually knows what causes this, please let me know... thanks....
------------------------------------
Reply:
------------------------------------
Reply:
This is a problem with Windows Vista when you update to SP1.
Rejoining the Domain (reregistering) may solve the problem.
Click on Computer.
Right Click Properties.
Under Computer name, domain, and workgroup settings-
Change Settings
Under to rename this computer its domain or
workgroup, Click Change.
Under member of:
Domain
Enter your domain name.
Click O.K. and restart system.
You haven't changed anything, but reregistering your system with your domain MAY solve the problem (it did with my system).
There obviously are issues when you update the OS that caused the problem.
As I always say, if in doubt, reboot. Cleaning out the system by doing this seems to work in many cases.
------------------------------------
Reply:
I experienced a similar problem with our Terminal Server 2008 farm, i could log on using a domain account from the host domain but when trying from a trusted domain it failed with the above error.
What Microsoft implemented in SP1 for both Vista and Server 2008 was a design change to address security concerns regarding a downgrade attack. Therefore, if the type of domain trust is NT4, no failover to NTLM authentication will be performed after the Kerberos authentication failed, which results in the logon failing with the above message.
Upon checking the trust status using replmon all the failing domains were of the type DOWNLEVEL, i.e. NT4, rebuilding the 2 way trusts from a Windows 2003 DC and enabling SID filtering allowed trusted domain accounts to log on to the Terminal Server 2008 farm.
So check any domain trusts, especially if they were in place prior to Windows 2000 SP4 and make sure the type is NT5 i.e. UPLEVEL
------------------------------------
Reply:
If you see your computer name/hostname on the AD by searching on the computers and still the error will appear just delete your computer on the AD list of computers then try to disjoin and join on the network.
My OS is a VISTA PC also.
mykeel
------------------------------------
Reply:
Join to Workgroup
reboot
log in as Administrator
Change computer name
Join to domain
reboot
Login to domain
------------------------------------
Reply:
we have an non rfc compatible domain name because of the company owner ...
dhcp an dns is running under linux, the domaincontroller is an dns slave (all so stupid, i know but not my work!)
so if i added a vista busines computer to the domain you could login after the first reboot (no domainsuffix registed) but not after the second reboot because of the domainsuffix is added later by the domaincontroller
thanks a million!
6 working hours to solve the problem because of non rfc compatible installations in our network
------------------------------------
Reply:
Hi Manny
Try this out on your Domain Controller:
A) Start > Run > ADSIEDIT.MSC
B) Go to Domain Partition and mark the affected computer
C) Rightclick and Properties.
D) Doubleclick ServicePrincipalName
E) Add new value: HOST/yourcomputername.yourdomain.xyz or whatever HOST is missing.
Best wishes
Roberto
------------------------------------
Reply:
Hi Manny
Try this out on your Domain Controller:
A) Start > Run > ADSIEDIT.MSC
B) Go to Domain Partition and mark the affected computer
C) Rightclick and Properties.
D) Doubleclick ServicePrincipalName
E) Add new value: HOST/yourcomputername.yourdomain.xyz or whatever HOST is missing.
Best wishes
Roberto
This solution worked for me also.
Note: Problem was caused when the primary DNS suffix was changed from the default Domain suffix.
Rblend
------------------------------------
Reply:
I detected this issue too after rebuilding one of my development servers. I had a server named USTRSCTC002 that belonged to my development domain dct.com. I unjoined the machine from the domain when it still had Windows Server 2003 on it, and then rebuild the machine to Windows Server 2008. Do bear in mind that Windows Server 2008 RTM is actually Server 2008 Service Pack 1, released in conjunction with Vista SP-1.
When I rejoined the machine to the domain, I was greeted with the error message "the security database on the server does not have a computer account for this workstation trust relationship."
I also noticed that for every logon attempt with a domain ID, I'd get a Kerberos error in the log. I originally didn't pay much attention to this error, but after trying everything that folks said to try (including multiple domain unjoin/rejoin attempts), and having nothing work, I decided to look into the Kerberos error some more.
Description:
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 11:28:8.0000 6/25/2008 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Extended Error: 0xc0000035 KLIN(0)
I looked up the KDC_ERR_S_PRINCIPAL_UNKNOWN and got hits across the board. There were no quick solutions there. But the 0xC0000035 error provided a much faster insight. 0xC0000035 maps to the symbolic name STATUS_OBJECT_NAME_COLLISION. That was interesting...where did I have a conflicting named object in my Active Directory?
This thread shed some light on the subject, and also provided a command to check for dupes: http://social.technet.microsoft.com/Forums/en-US/systemcenter/thread/be6fcac4-7310-42d1-980e-e1725b464756/
This command was in the above mentioned thread and is provided here for convenience:
ldifde -f C:\SPNs.txt -t 3268 -d dc=domain,dc=com -l serviceprincipalname -r (serviceprincipalname=*) -p subtree
I went through the results and checked for the conflicting name, in this case "ustrsctc002" or "ustrsctc002.dct.com"
Several years ago we were beta testing Windows Vista and had rebuilt this machine to Vista build 5270, and after having problems with it, we rebuilt it to Server 2003--and forgot to unjoin it from the domain.
Years later, the old Vista Dev Server computer record was still lingering in the AD. I was able to find it in ADSI Edit. Basically I had two different Computer objects possessing the same servicePrincipalName value(s). My USTRSCTC002 machine object was correct:
HOST/USTRSCTC002
HOST/USTRSCTC002.DCT.COM
TERMSERV/USTRSCTC002
TERMSERV/USTRSCTC002.DCT.COM
But my old Vista Dev Server had the following for servicePrincipalName:
HOST/Vista Dev Server
HOST/USTRSCTC002.DCT.COM
TERMSERV/Vista Dev Server
TERMSERV/USTRSCTC002.DCT.COM
It was the instance of HOST/USTRSCTC002.DCT.COM that was the killer.
It is my understanding that Vista SP-1 and Server 2008 have an affinity for Kerberos over NTLM, and will use it if available. That said, since this was a fresh Server 2008 build which wanted to use Kerberos, the old computer record that was hanging around was the downfall. Once I deleted the offending computer object (the Vista Dev Server), life was good. :)
Best regards,
Matt
------------------------------------
Reply:
I used your idea..it is working....thnks man..keep in touch..my id us shuanak312@gmail.com
------------------------------------
Reply:
This is a reply to the post by Matthew Sawyer...YOU ARE THE MAN! Thank you!!
I ran ldifde -f C:\SPNs.txt -t 3268 -d dc=domain,dc=com -l serviceprincipalname -r (serviceprincipalname=*) -p subtree on my DC and I found the problem. Once I deleted the offending computer, I was able to login to my other DC.
------------------------------------
Reply:
Could someone sujjest.
what will be resolution for Windows 7
------------------------------------
Reply:
------------------------------------
Reply:
My situation:
Old staff file server was renamed in AD to SSS4-OLD from SSS4 and then rebooted as well as IP changes, etc. I then made a new server (in our VMWare cluster) as a Server 2008 SP2 Standard Edition named SSS4 (replacement server).
I could join the domain, but not login getting that server security database error. Thanks to the some of the other posters here, I checked the SPN on the new SSS4, and it was fine, however, the old SSS4-OLD had not changed it's SPN. Upon changing the SPN and rebooting the new SSS4, everything is now fine.
Thanks for the help in pointing me to the right direction.
------------------------------------
Reply:
I've seen this error come up and resolve itself after renaming a computer, re-joining it to thedomain and I've seen it just go away on it's own. I don't have a single clue as to what is going on? Has Microsoft chimed in on this yet?
The are 3 domains in the forest I'm working in. All servers are 64bit 2008 standard. There is a trust with another forest hosting 1 domain. Computer accounts are typically created in AD first. These are new machines in a new domain using a new naming scheme. I know there are no duplicates.
------------------------------------
Reply:
Good luck,
Paul Li
------------------------------------
Reply:
Fortunately I was able to get back in using Safemode (no networking) which allowed me to access the event logs. The event logs indicated Kerberos errors and I ended up have to shut off the Kerberos and DNS services to get back in. Later I did find a rogue AD entry that looks like it was create when the server was promoted. Removing that resolved the issue.
The fact is that a lot of people are having this issue and no-one has a clear reason why it's happening or a sure fire fix for all situations. This appears to be a pretty big bug and I'm amazed it hasn't been addressed yet.
------------------------------------
Reply:
------------------------------------
Reply:
Even tried to upgrade to SP2 the Vista PC and still not able to join the domain. Will try a format on the PC even i cannot find anything soon, and prolly will install winXP,
------------------------------------
Reply:
During this project I noticed some of the servers exhibiting these symptons just fixed themselfs after about half a day which to me strongly suggests a replication issue. I was pretty careful to make sure I was only making changes on the DC the servers were logging into however this problem still occured. After a while, this problem stopped happening altogether.
The only thing can think of was I made some major changes to AD sites and services. Sites and Services was selecting replication partners that physically couldn't talk to either due to firewall policies or lack of established tunnels. I gave the default site link a ridiculously high cost and then started modelling out the perferred replication paths so the DC's could actually communicate with each other. (It's also neccessary to delete the automatic links that couldn't communicate - If they keep reappearing then you have more work to do.) This smoothed out almost all of the AD replication issues and I haven't seen the security error on the last 8 server installs.
I don't know if this is the end all solution, but it's another avenue you can explore.
------------------------------------
Reply:
I found myself in the same situation. In fact I have renamed a decomissioned server but I omit to do a restart and just did a lazy shut down. After lookin at your post and the event viewer I found a eventID 11 from Kerberos-Key-Distributoin-center (source). The source of my problem was a duplicate SPN on the DC (SBS 2K8). I found a procedure to fix the problem from microsoft here:
http://technet.microsoft.com/en-us/library/cc733945(WS.10).aspx
Hope this help.
Best regards,
Pierre
Pierre Sioui
------------------------------------
Reply:
------------------------------------
Reply:
1. Delete primary DNS suffix in Computer Name dialog window and reboot.
2. Set primary DNS suffix equal to domain suffix and reboot server again.
After these steps I was able to logon with domain user credentials on that server.
------------------------------------
Reply:
------------------------------------
Reply:
Another case:
It's computer conflict in Domain, so just change the computer name unique and rejoin the domain, the problem will be solved.
Cheers Roberto,
Kevin
------------------------------------
Reply:
------------------------------------
Reply:
I spent a week and a half on this issue, only to find out how silly my situation was. In my office I have to use a switch so that I can work on different PCs at the same time. It finally donned on my that maybe the switch was the problem. Sure enough, I took the Vista SP1 laptop that into the server room and connected directly to the network from a main switch and now everything is just fine. I've not had problems with XP being setup in my office over the secondary switch, but for whatever reason Vista wouldn't function properly...
fat
------------------------------------
Reply:
Dear Matthew,
Thanks for your explanation. My problem are the same, but the problem resides on duplicate SPN in the Active Directory Objects.
I have 2 SPN pointed to SMTPSVC/COMPUTERNAME, thats cause the 2 Exchange Servers do not communicate each other.
The problem get 2 days of my work and your ldifde command saves more works days.
Thanks again.
Paulo Hecko
MCSE, MCP, MCTS.
------------------------------------
Reply:
Surely just the simple way as I have just done for two machines that I have the issue with is to run the joining network wizard within change settings for domain/computer name etc.
As long as you know the name of your domain and know the username and password of an administrator of that domain it will then re-add the machine to the domain.
------------------------------------
Reply:
------------------------------------
Reply:
I was able to fix this issue on a laptop with windows 7 Pro 64bit OS by logging-in as another user with administrative rights and simply detaching and re-joining the domain.
------------------------------------
Reply:
I had the same issue on one of my remote site domain controller (it was a new installation). After my R&D I found one thing, in AD there were two computer accounts for single domain controller. First one is displayed as "workstation or server" and second one is dispalyed as "writaable domain controller". I just deleted the computer account which is having a machine role of "workstation or server" then immediately I was able to login.
Santhosh Sivaraman MCITP: Microsoft Exchange Server 2007/2010 | MCSE/MCSA
------------------------------------
Reply:
I had the same issue on one of my remote site domain controller (it was a new installation). After my R&D I found one thing, in AD there were two computer accounts for single domain controller. First one is displayed as "workstation or server" and second one is dispalyed as "writaable domain controller". I just deleted the computer account which is having a machine role of "workstation or server" then immediately I was able to login.
Santhosh Sivaraman MCITP: Microsoft Exchange Server 2007/2010 | MCSE/MCSA
------------------------------------
Reply:
Hey
Good News. I just have sorted the problem out.
I have one dedicated server for file, application and print services on Windows Server 2008 R2 Enterprise 64 bit. I normally joined this member server under our Domain. Suddently i was facing this problem while i started workshop. I could not join the server under domain after doing lots of changes. Everytime the same messege appeared "The security database on the server does not have a computer account for this workstation trust relationship." While i was going through MSDN this problem blog i was trying to solve this issue and i solved it.
I just simply joined the computer under workgroup and than restarted.
Than i logged on locally as an administrator and changed the computer name to a different name and clear the dns suffix and netbios computer name.
Than again i restarted the computer and logged in as local administrator.
Than i tryed to join the computer under domain and it allowed me join under domain but you have to put administrator previleges.
Than restarted the computer again and put domain administrator account and logged in under domain. I logged in successfully.
I think this will help you a lot. If you do lots of changes on your domain controller or dns server than server holds the old legacy cache information sometimes even after flashing the cache information from the server it doesnot help us to get rid of the old information.
Anyway i solved my problem the way i explained you. Try it hopefully it will work. Good Luck
Best Wishes
Abu Tareq Mohammad Zobayer
------------------------------------
Reply:
------------------------------------
Reply:
Hello,
There are, unfortunately, a number of factors that contribute to this error being generated. Although the Win7 machine may have *looked* like it successfully joined the domain (after all, a Computer object exists in AD), in fact the joining wasn't entirely succuessful. That is, yes, the Computer object gets created, but it is not fully and correctly configured. This can be due to myriad reasons - firewalls enabled, cloned machines, conflicting product keys/sids etc. etc.
When joining Win7 machines to a pre-AD2008 domain, always make sure all Windows firewalls are turned off on the machine, and have one and only one network route to the domain controller (e.g. don't enable the wired network and wireless).
If you get this error: "The security database on the server does not have a computer account for this workstation trust relationship." when attempting to login, this is usually because the Computer object creation did not complete (you may have seen a DNS or similar error after joining the domain). This means the object is created, but important LDAP attributes are not set in the object. So...to set these, try this:
On your Domain Controller, get hold of ADSIEDIT.MSC. If you don't have it, you can download it from the Microsoft Support Tools site.
RUN: Start -> Run> ADSIEDIT.MSC
Under the Domain tree, find the Computer object in question and select Properties. When you see the list of attributes for the machine - and it should be a fairly long list - you need to change these 2 attributes:
dNSHost
If you've seen the trust error, this attribute's value will probably be blank or incomplete. Change the value to the fully-qualified DNS name of the machine as shown in the machine's System properties - e.g. mywin7box.mycompany.domain
servicePrincipalName
This attribute takes multiple values. Again, if you've seen the trust error, it will likely be blank. You need to add 2 values to this attribute:
1. HOST/the computer's MACHINE NAME in all capitals (NOT the FQ DNS name) - e.g. HOST/MYWIN7BOX
2. HOST/the computer's fully qualified DNS name - e.g. HOST/mywin7box.mycompany.domain
NOTE the use of a FORWARD slash, NOT a BACK slash, as is often used in MS naming (thankfully, this is LDAP)
Press OK to save the changes, and you should then be able to login via the domain on the Win7 box.
I really hope this horrible hack helps people get to grips with the 'new and improved' Win7 (Vista.1) networking.
-midiman-
------------------------------------
Reply:
------------------------------------
Reply:
This problem was resolved with the below simple steps.
1) REmove the system from Domain.
2) Set the DNS suffix correctly. Ensure that you have all the suffix set correctly especially for the domain where you log in.
3) Add the system back to domain.
My guess is, if the DNS suffix is set up correctly before adding the system to the domain, this error/problem can be avoided.
Regards,
Chandan Patralekh
------------------------------------
Reply:
I have run into this issue repeatedly on Server 2008 R2 and Windows 7 machines. Checking the DNS suffix with ADSIEDIT showed that both the correct entries were there. There are a few ways I have found to resolve this issue.
1. Reboot the 2008R2 DC - not the best of fixes as it will cause other issues
2. Reboot the computer - seems to fix the issue 90% of the time, until it happens again.
By far the easiest way I have found to get around this issue:
When logging into your domain. When you receive this error, Instead of using user/pass/domain change your login name to user@domain/pass, or vice-versa This little work around has worked for me every time.
Hope this will help some folks, I was hoping SP1 would have fixed this issue, but no, its still around.
------------------------------------
Reply:
Now, all clients (WinXP) can connect and use the server resources but everytime they connect to sever, following errors are logged:
Event ID: 5513 The computer COMP1 tried to connect to the server \\SERVER using the trust relationship established by the EXAMPLE domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship.
Event ID: 2723 The session setup from computer 'COMP1' failed because the security database does not contain a trust account 'COMP1$' referenced by the specified computer.
Event ID: 5805 The session setup from the computer COMP1 failed to authenticate. The following error occurred: Access is denied.I tried to re-join the client machine from client, but by doing so it creates separate user profile folder in 'Documents and Settings', and user's earlier preferences are gone.
Will solution suggested by Roberto.Pascolo solve my problem? or Is there any other way to re-join client machines to the domain?
Thanks in advance.
------------------------------------
Reply:
Hi MannyHelped to cope with the problem in my case.
Try this out on your Domain Controller:
A) Start > Run > ADSIEDIT.MSC
B) Go to Domain Partition and mark the affected computer
C) Rightclick and Properties.
D) Doubleclick ServicePrincipalName
E) Add new value: HOST/yourcomputername.yourdomain.xyz or whatever HOST is missing.
Best wishes
Roberto
Are there plans to release fixes?
------------------------------------
Reply:
Hi Everybody,
I do have the same problem with different Windows 7 machines. Once in a while different workstations can´t log on. they get the error:
The scurity database on this server does not have a computer accout for this workstation...
The Computer account is there, also the right ServicePricipalName. This happens one day and then for weeks there is no problem with the logon. Then again, and next day everything is fine. I tried all the different sollutions provided here. But the problem stil persists.
Does anybody have an idea?
Thanks
Juergen
------------------------------------
Reply:
Hi,
we had a same problem with couple of (virtual) servers. These was cloned, from the one working host, and had some SPN:s was setup for the servers. After rejoining from domain (several times....) did not help (with the same name) we changed the name of the servers and then (from server-x to server-xx) they started working. Reason was propably that, the SPN holds the SID information, and therefore those servers could not login with old name.
Now servers are workig fine. Just needed to reconfigure SPN:s to get services working as expected.
------------------------------------
Reply:
Manny,
try to remove the workstation from the domain and make it a 'workgroup' box. then restart and rejoin to the domain. then restart and see if it works (I am not saying that this is pretty but the only way to make it work for me on one of the machines).
peter
This worked for me!
Thnx
------------------------------------
Reply:
If you can't logon, how would you achieve this?
------------------------------------
Reply:
Sure to change the name and rejoin the domain works for a while, but than all of a sudden, the workstation can´t log on. Than for one or two weeks it works again, and the again I get the error that no computer account is there.
Since months I look for a solution, so far without success.
If someone out there has an idea it would be great.
Juergen
------------------------------------
Reply:
Hello PKSB
Can you point me to exactly where the computer configuration is? I just see system configuration which does not contain administrative templates... please excuse my slowness :)
------------------------------------
Reply:
Hello all, hope my little contribution may help someone.
I started getting this error after cloning a member server. When I cloned my 02 server to create a replacement for my ailing 03 server, I ran into this error when I turned off the ailing server and renamed the new one with the name and ip of the original sick server.
- after reboot, my application would no longer work on the new server. The client would give a generic aspx error, and say unavailable.
- Discovered that although the server indicated it joined the domain, it would not allow logons with any domain accounts. It gave the error above that brought us here.
- discovered that AD would not/could not create a computer account for the new server.
- finally decided to create a computer account manually in AD. Tested, but it still didn't work.
- Then using info from the posts here, edited the serviceprinciplename value in the manually created AD account, using the ADSIEdit tool. I also edited some other values that involved server names, etc.
- after editing the values for the new server, using another good server as a guide, saved the changes and I tested again and the server worked.
Thanks to Roberto for mentioning the servicenameprinciple in his post, that guided me to what was wrong.
------------------------------------
Reply:
Hi All,
I am getting this error for past few days on Windows 7 .At the time of giving the credentials just off the wireless and you can bypass this error.But this is a temporary solution.Once you have access you can look for a permanent solution.
Looking for a permanent solution.Can anybody help me out (:
------------------------------------
Reply:
I found I needed to do this to get it all working
From a DC/AD server
ldifde -f C:\SPNs.txt -t 3268 -d dc=domain,dc=com -l serviceprincipalname -r (serviceprincipalname=*) -p subtree
In the above command, replace DC=domain,DC=com with the DN of the domain. To check if duplicate SPN is present.
for me the issue was a duplicate HOST/ entry for the server found in a service account
------------------------------------
Reply:
------------------------------------
Reply:
------------------------------------
Reply:
Hey, Rblend, How Can I change primary DNS suffix on a DC?
PaulJSO said:
Roberto Pascolo said:Hi Manny
Try this out on your Domain Controller:
A) Start > Run > ADSIEDIT.MSC
B) Go to Domain Partition and mark the affected computer
C) Rightclick and Properties.
D) Doubleclick ServicePrincipalName
E) Add new value: HOST/yourcomputername.yourdomain.xyz or whatever HOST is missing.
Best wishes
RobertoThis solution worked for me also.
Note: Problem was caused when the primary DNS suffix was changed from the default Domain suffix.
Rblend
------------------------------------
Reply:
------------------------------------
Reply:
Hi Roberto,
I just tried your workaround and it worked perfectly.
Many thanks!
Kind regards,
Buz
Phil. B.
------------------------------------
Reply:
------------------------------------
Reply:
Just a follow up to the cause of this error for our Agency.
Some of our Agency computers were connecting to remote portals using Connectix or Citrix software. What was happening was the remote location was adding a "Domain" suffix to the computers that were connecting. These computers would then try to login using the "default" domain suffix that was now incorrect.
I fixed this issue by using a GPO and forcing our domain suffix to be the primary suffix. I have not seen this error since I have made this change.
If you were to look in the computers "Advanced TCP/IP" DNS settings you will probably find the offending domain suffix.
Might not be everyones problem but it sorted mine out.
------------------------------------
Reply:
Hi
Please help - I'm getting crazy. Four machines, after SP1, two with this login problem. I'm getting the message "The security database on the server does not have a computer account for this workstation trust relationship.". I updated the network card driver, I removed computer from domain and rejoined. Nothing helps.
First login works fine, second one gets the error message again. Please help. User and I don't know what to do!
Any help would be appreciated.
Best wishes
Roberto
I have an easier way. Log into the AD server goto workstations and manage that computer. In there you can add a local user or enable/reset the password on that workstation. If you can NOT find the workstation name Add it (the same one that it used to have) You cna tell what that is by trying to log into the computer that is giving you the Security error. Choose other user and you'll see what the computer name was
Now once you have enable the admin account or found what another local account was you can go back to the workstation login locally and then re-add yourself to the domain. One reason the security database lost the computer account is because there might be two computers with the same name. maybe the old one was recently turned back on??
Goodluck!
------------------------------------
Reply:
How I fixed it:
I had this problem on a Windows 7 workstation, connecting to a Windows 2008 SBS server. I could only login to the workstation by unplugging the network cable, then plugging it back in once the PC logged in. But once on I couldn't access that server.
I could ping the server's IP address, but I couldn't see the server at all. I could see other computers on the network, just not the server controlling the domain.
I Googled the problem and followed various solutions, none of which worked. (Like disconnecting it from the domain, renaming the computer, then reconnecting it to the domain... which didn't work because it couldn't find the domain controller. After this I did a System Restore to put things back to how they were.)
I finally modified the hosts.ini (C:\Windows\System32\drivers\etc\hosts.ini)
In my case, with the server's IP being 192.168.0.200 and the server name being TrackServer I added the following line to the hosts.ini file:
192.168.0.200 //Trackserver
Poof! After that it worked beautifully. I could login to the domain and access the server fine.
I assume something screwy happened to the DNS on that computer. This system has about 15 computers on it, and all but 4 have XP. This is the only one of the 4 Windows 7 PC's that have had the problem.
------------------------------------
Reply:
Any update from Microsoft as to when we can expect a permanent solution to this problem? Also maybe a reason for why this is happening?
I have this problem on my networt on different PC's at random times.
CVR
------------------------------------
Reply:
- Edited by C_J_GO Monday, February 6, 2012 5:50 PM
------------------------------------
Features MDT V/S SCCM OSD
mohd.w
- Edited by Md.Waseem Wednesday, February 8, 2012 1:05 AM
Reply:
Depends on how you look at things. The question isn't necessarily the correct one to ask though because the two solutions are not mutually exclusive. MDT works in two ways:
- Stand-alone (often called lite-touch)
- Integrated with ConfigMgr (often called zero-touch)
So, for the things that MDT does above and beyond what ConfigMgr OSD does out of the box, you would just integrate it into ConfigMgr.
The reverse is not true however, there are many, many things that ConfigMgr does that MDT does not so if you have ConfigMgr in place, it would be somewhat silly not to use it and integrate MDT into it.
Jason | http://myitforum.com/myitforumwp/community/members/jasonsandys/ | Twitter @JasonSandys
------------------------------------
Reply:
Hello Jason,
You are correct, MDT Works in two ways as you described above. Actually i was trying to differentiate it only with OSD deployment feature.
If i have SCCM in place should I integrate MDT also or SCCM can do ZTI without MDT.
Thanks
mohd.w
------------------------------------
Reply:
ConfigMgr OSD can absolutely get the job done without MDT.
However, MDT adds a lot of great functionality. Basically, things that a lot of folks would write/create on their own is already provided by MDT for easy reuse.
Also, integrating MDT into ConfigMgr doesn't mean you have to use the MDt functionality, it just means it's now available for use. So I would defintiely install it and evaluate the things it gives you against those that are often characterized as "missing" from native ConfigMgr OSD.
Jason | http://myitforum.com/myitforumwp/community/members/jasonsandys/ | Twitter @JasonSandys
------------------------------------
Alert history time vs. alert created property
I'm looking for an explanation for the difference of time between the alert history tab "alert activated by the system" value and the "created" property value on the alert itself.
My example is logical disk free space. It appears the alert history tab shows when the alert opened by the system and the created property for the alert aligns with a sample of the logical disk free space (doesn't appear to be up to date with now, it stops pulling in the most recent sample for some reason). Again, the sample is NOT the most recent it's just some point in time so I was looking for some clarification around how this works.
Example of situation:
Alert for Logical Disk:
- Time in Alert history where alert was opened by system: 1/1/2012 5:10pm
- "Created" property of alert: 1/1/2012 5:25pm
FIM 2010 Hotfix Installation - Error 25070 These workstations have sessions with open files on this server
FIM 2010 Hotfix Installation - Error 25070 These workstations have sessions with open files on this server: http://social.technet.microsoft.com/wiki/contents/articles/7214.fim-2010-hotfix-installation-error-25070-these-workstations-have-sessions-with-open-files-on-this-server.aspx
Timothy P Macaulay, MCSD, MCSD.NET, MCAD, MCP
Converting UNIX date/time bigint value to SQL DateTime format
Hi all,
We have a database that stores a UNIX epoch value in a BIGINT field. It's a hassle to continuallly type out the appropriate conversion code to show the human-readable date and time. So here is a function that I created to handle the task. I hope this is helpful to others.
CREATE FUNCTION dbo.udf_ConvertUnixDT2SqlDT ( @unixDT BIGINT, @GMToffset INT ) RETURNS DATETIME AS BEGIN DECLARE @epoch DATETIME DECLARE @retDT DATETIME SET @epoch = '1/1/1970' SET @retDT = DATEADD(hh, @GMToffset, DATEADD(ss, @unixDT, @epoch)) RETURN @retDT END
The first input is the UNIX epoch value to convert. The second value allows you to adjust the return value to reflect the targeted timezone. Below is a sample usage statement.
select dbo.udf_ConvertUnixDT2SqlDT(<UNIX timestamp field name>, -5) as datevalue, * from TableName
Example datevalue: 2012-02-01 13:41:21.000
Reply:
Jian Kang,
I see that you changed the type for my post. Can you tell me what changed? This was my first post and I'd like to learn more about how you organize posts.
Kind regards,
Steve
S
------------------------------------
Reply:
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
------------------------------------
Reply:
S
------------------------------------
Reply:
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
------------------------------------
Reply:
S
------------------------------------
FIM 2010 - Working with the Recycle Bin Feature in Windows Server 2008 R2 Active Directory
More of an information, central location wiki on FIM 2010 working with Windows Server 2008 R2 AD.
FIM 2010 - Working with the Recycle Bin Feature in Windows Server 2008 R2 Active Directory: http://social.technet.microsoft.com/wiki/contents/articles/7262.fim-2010-working-with-the-recycle-bin-feature-in-windows-server-2008-r2-active-directory.aspx
Timothy P Macaulay, MCSD, MCSD.NET, MCAD, MCP
FIM 2010 - Installation Companion - Accounts
So in support we do receive a lot of installation type calls. One thing that is discussed is the accounts needed for the installation. I decided to throw together a wiki that has the accounts needed. The goal of the article is to provide a list of accounts that is recommended to be created, and if possible prior to installation to help the install go by faster. It is a companion type article to the installation guide.
FIM 2010 - Installation Companion - Accounts: http://social.technet.microsoft.com/wiki/contents/articles/7222.fim-2010-installation-companion-accounts.aspx
Timothy P Macaulay, MCSD, MCSD.NET, MCAD, MCP
- Changed type Tim MacaulayMicrosoft employee Monday, February 6, 2012 4:37 PM wrong type
- Changed type Tim MacaulayMicrosoft employee Saturday, May 26, 2012 5:51 PM
IIS Management Pack - Default website cannot be started (port 80 in use)
Hello everyone,
Since this is my first post on this forum, this might not be the appropriate subforum for this discussion. I couldn't find one which would be more suitable though. On the other hand, i believe SCOM users and administrator might be more familiar with this issue than IIS admins.
This situation takes place in a relatively large domain with fairly new Microsoft products, including SCOM 2007R2 CU5. SCOM uses the IIS Management Pack to monitor several servers. The IIS Management Pack also monitors the Default Website, assigned to port 80, and will present an alert in case the website is not running or is unable to start. (The IIS 7 web site named Default Web Site on server.domain.com is unavailable as the site has been stopped.)
Then, there also other system administrators who are hosting websites on the IIS servers, using port 80 of 443. Without using host headers, only one website can use port 80 so one of both sites cannot be started. Since the IIS admins prefer to run their website on port 80, the Default Website cannot be started.
With >500 servers running IIS, how would you prevent this situation from happening? Ask all IIS admins to use different ports? Use host headers? Assign the IIS Default Website to use a different port? Or is there another option which hasn't crossed my mind?
Many thanks and regards,
Martijn
- Edited by MWeterings Monday, February 6, 2012 4:05 PM
asus m4a88t-m express gate problem feb 05 2012
My problem is about Express Gate
I was make a homework in my pc when i encounter some problem,
it's "not responding" of other program...
i use "ctr + alt + del" to force end task but it's not easy to stop....
So i force to restart my PC when booting i'ts show's "disk read error press ctr+alt+del"
i turn off the PC and open it, when boot it's appear "express gate loading" then nothing happen...I look up in "BIOS" it's already disabled...
So why they required the express gate?
When i install the Operating System i already did not install the driver of express gate so that they will not appear forever i don't want to use that...
And now it will appear again...how can i stop that thing...
is this asus board required to install driver of express gate?
hope can save my problem as now i can't use my PC cause of express gate always boot not in windows instead....
Reply:
You are on the wrong website. This is a Microsoft website.
Express Gate is an ASUS product and feature. It is not a Windows 7 feature nor a Microsoft product!
For problems with ASUS products, you must go to the ASUS website forums or contact ASUS Technical Support.
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. "
------------------------------------
Kundly 2009 compitibility problem with the Windows7.0
Reply:
You will have to contact the publisher of the program because this program is not compatible with Windows 7.
The publisher of the program will have to give you the needed information, not Microsoft!
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. "
------------------------------------
Fabric Management in the IaaS Private Cloud Article
Fabric management is a key indicator of success for IaaS Private Cloud. Private cloud is all reaching a high level of maturity when it comes to service management, since your IT group is now in competition with public cloud providers. Improve your fabric management game! Check out "Private Cloud Infrastructure as a Service Fabric Management" to learn more - and then let's talk about the article here.
Thanks!
Tom
MS ISDUA/UAG DA Anywhere Access Team Get yourself some Test Lab Guides! http://blogs.technet.com/b/tomshinder/archive/2010/07/30/test-lab-guides-lead-the-way-to-solution-mastery.aspx
SWIFT standard Developer Kit (SDK) adoption
Hello
as you know SWIFT is now suport converting SWIFT MT into XML format by using tool called SDK https://www.swiftcommunity.net/communities/245/detail
my question is : is thier any plan in the coming future to see the same XML ()
because the generated XML form SDK is different than the XML coming from A4SWFIT
- Changed type Lloyd Zhang Monday, February 6, 2012 2:38 AM
Reply:
That is a good suggestion for a future A4SWIFT version. I am not sure if there are any plans to do that.
Thanks,
If this answers your question, please use the "Answer" button to say so | Ben Cline
------------------------------------
Reply:
------------------------------------
Kjell Uppheim-administrator
Hi.
During this weekend my exchange system with outlook is changed to office 365. And it is working. Meanwhile, we find different computers with different display in "Microsft Online Services Sign in".
In one computer we can see "My Company Portal" after signing in. In this computer we can separately open Office 2010/Outlook and be asked for password etc. and then work in Outlook as before.
In another computer we can see "My Company Portal" and " E mail and Calendar". Here we can choose between working in Outlook 2010 or work on the web.
In another computer we can see only "My Company Portal" and when trying to open separately Outlook 2010, it opens but with message-not connected.. There is no place to connect.
What are we doing wrong.
Best regards,
Kjell Uppheim
